-
Notifications
You must be signed in to change notification settings - Fork 37.7k
build: Fix Qt link issue for macOS target with DEBUG=1 #18117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Gitian builds
|
Can you explain why this is needed? Why is only building the debug libraries in debug mode not good enough for MacOS?
I mean, this is not really a downside if it doesn't work otherwise! |
For macOS targets with
This causes that the following checks bitcoin/build-aux/m4/bitcoin_qt.m4 Lines 330 to 342 in ac5c5d0
to fail due to the linker error:
With this PR both lib versions, |
Closed in favor of #18298 |
…s with DEBUG=1 76f52e3 build: Fix Qt processing of configure script for depends with DEBUG=1 (Hennadii Stepanov) Pull request description: This PR: - makes the `configure` script correctly pickup Qt if depends is built with `DEBUG=1`: - for Windows -- fix #19266 - for macOS -- fix #16391 - is an alternative to #18117 (without downsides) ACKs for top commit: fanquake: ACK 76f52e3. Tested native darwin, and darwin/win cross compile with `DEBUG=1`. Tree-SHA512: 8fde99302b4b06faf109315bddba9e3063b156c50f8f9863c2bd51718538c719429a63fdced071730c18022f2e559d3b25c1dcec3efa81fe79f657253680956a
Fix #16391
With this PR for macOS target, building
depends
withDEBUG=1
does not cause a linker error for Qt static plugins on the followingconfigure
script run.Qt docs refs:
The obvious downside is the increased compilation time for macOS targets with
DEBUG=1
.