Details
- Reviewers
deadalnix - Group Reviewers
Restricted Project
On OSX (or cross build):
ninja
Compare the size of the binaries src/qt/bitcoin-qt and
src/qt/BitcoinABC-Qt.app/Contents/MacOS/BitcoinABC-Qt (the later
should be stripped).
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- cmake_osx_strip_bundle
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 8058 Build 14111: Bitcoin ABC Buildbot (legacy) Build 14110: arc lint + arc unit
Event Timeline
src/qt/CMakeLists.txt | ||
---|---|---|
314 | Why do we need a bitcoin-qt target and this? This is a bit strange, because on every target, ninja bitcoin-qt will build bitcoin-qt, but on OSX, it will actually build a broken version of bitcoin-qt and I need to do ninja bitcoinABC-Qt to actually get the real deal. I think it is better to fix this rather than pile more on top of it. | |
350 | I find this a bit disappointing, as it prevent dependency tracking. If the command doesn't allow for it, maybe simpl copying the file and then running it in place could do the trick. |
src/qt/CMakeLists.txt | ||
---|---|---|
314 | I see them as 2 different things. The bitcoin-qt target is still a valid target (and is not broken) on OSX and builds the bitcoin-qt executable the same way that it is done on Linux. | |
350 | My understanding is that this signature of add_custom_command doesn't break the dependency tracking. |
src/qt/CMakeLists.txt | ||
---|---|---|
314 | It is a second executable that contains the exact same code, but in addition contains various OSX metadata. If we are on OSX, then that should be bitcoin-qt. Just likeon Windows, bitcoin-qt is enriched with some windows specific metadata. |
OK let's do this.
We are shipping both the executable alone and as a bundle as part of our releases, so it will require a copy which can be done when running the gitian build.