diff options
author | fanquake <fanquake@gmail.com> | 2021-03-24 16:52:04 +0800 |
---|---|---|
committer | fanquake <fanquake@gmail.com> | 2021-03-24 16:52:17 +0800 |
commit | f67b5dca576669bfed0cf4af9f2cc6273010a0d7 (patch) | |
tree | 86217e105226a696a17eb18430f5be04a538eeda /doc | |
parent | 7ce7ce5716c839c2988364c8356e8770795cce8b (diff) | |
parent | 3d31abbaaad599443ec5ffee90ddb6989a625277 (diff) | |
download | bitcoin-f67b5dca576669bfed0cf4af9f2cc6273010a0d7.tar.xz |
Merge #20734: build: Make platform-specific targets available for proper platform builds only
3d31abbaaad599443ec5ffee90ddb6989a625277 build: Make Windows-specific targets available for Windows builds only (Hennadii Stepanov)
92990e25b7e5d02651ffa27f2d57c4c2c190668e build: Make macOS-specific targets available for macOS builds only (Hennadii Stepanov)
Pull request description:
On master (f1dbf92ff0475a01d20170ea422c1d086acbbc57) it is possible to point `make` to macOS and Windows specific targets even the build system is configured to build for Linux platforms:
```
$ make Bitcoin-Core.dmg
...
$ make bitcoin-21.99.0-win64-setup
...
```
Such behavior makes no sense, and it is confused. Fixed in this PR.
ACKs for top commit:
fanquake:
ACK 3d31abbaaad599443ec5ffee90ddb6989a625277 - tested that nonsensical targets are no longer available. i.e
Tree-SHA512: bbd8450bf98fbccb0b828df2f753ed0dbbd203defa2f58ce21390ee2ea183c95d8ff585d62d52be870dbf0158e2bb0fbd47eda026b80174ee6fd617473f5ac03
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions