Fixes issue #16909 to update the contrib/macdeploy/README.md to match the files produced from make deploy
The files produced from make deploy are as follows:
Bitcoin-Qt.dmgBitcoin Core.appdist/Bitcoin Core.app
10 | @@ -11,5 +11,5 @@ This script should not be run manually, instead, after building as usual: 11 | During the process, the disk image window will pop up briefly where the fancy 12 | settings are applied. This is normal, please do not interfere. 13 | 14 | -When finished, it will produce `Bitcoin-Core.dmg`. 15 | +When finished, it will produce `Bitcoin-QT.dmg`, `Bitcoin Core.app` and `dist/Bitcoin Core.app`.
s/Bitcoin-QT.dmg/Bitcoin-Qt.dmg/
Updated, thanks 👍
Thanks. Can you please update your commit message to something like the PR title.
10 | @@ -11,5 +11,5 @@ This script should not be run manually, instead, after building as usual: 11 | During the process, the disk image window will pop up briefly where the fancy 12 | settings are applied. This is normal, please do not interfere. 13 | 14 | -When finished, it will produce `Bitcoin-Core.dmg`. 15 | +When finished, it will produce `Bitcoin-Qt.dmg`, `Bitcoin Core.app` and `dist/Bitcoin Core.app`.
Two .apps? Is this intentional?
I think it'd make sense to make this a list, and describe what each item is (and what the differences are)
The two .app files were intentional as both are created, one in the root folder and the other is in the dist.
I am unsure of the differences between these two .app files, so any insight into this would be appreciated
OK—I think there's a misunderstanding about the purpose of this documentation. The idea here is not to list every intermediate that will be included in the image, but only the end product of the macdeploy (the .dmg image). If the purpose of the intermediate files is not clear, better to not list them.
Done and squashed the commits 👍
ACK 4441e58497513cc55cfebfdcaaeee340f62f8062
ACK 4441e58497513cc55cfebfdcaaeee340f62f8062 - checked that Bitcoin-Qt.dmg is produced.