Task #2244
closed
Allow compilation against statically compiled libraries
Added by Alex Afanasyev almost 11 years ago.
Updated over 10 years ago.
Description
waf has a "feature" of not propagating static libraries in "use" variables of build targets.
This effectively means that we need to specify use='BOOST CRYPTOPP SQLITE3' for every build task that actually uses boost, cryptopp, and sqlite3 libraries (e.g., all test cases).
I have a patch for this issue, but I'm having doubts whether to actually submit it or not. For completeness, I can submit the patch, but statically compiling binaries is kind of weird and shouldn't be really encouraged.
Originally, this feature was needed in the first attempt to cross-compile code on Android platform. However, it will not be needed in the future (there are no restrictions on using shared libraries and I have no idea why instructions on the Internet we followed suggested static libraries...).
- Status changed from New to Code review
- % Done changed from 0 to 100
- Subject changed from Allow compilation against statically compiled boost libraries to Allow compilation against statically compiled libraries
- Description updated (diff)
- Target version deleted (
v0.3)
- Status changed from Code review to Abandoned
I decided to abandon this. Instead, I'm thinking to provide ability to avoid library detection and use only explicitly specified flags.
Also available in: Atom
PDF
Updated by