|
Boost : |
From: Daniela Engert (dani_at_[hidden])
Date: 2024-05-02 14:07:02
Am 02.05.2024 um 15:07 schrieb Nigel Stewart via Boost:
>>> Our specific requirement is to statically link _our_ preferred version
>> of zlib
>>> built from _our_ pristine (and possibly patched) repo.
>> As I said, this is accomplished by putting the following line in one of the
>> b2 configuration files, for example user-config.jam:
>>
>> using zlib : 1.3.1 : <include>/opt/zlib-1.3.1/include
>> <search>/opt/zlib-1.3.1/lib <name>our-zlib-name-1.3.1 ;
>>
> Peter,
>
> Thanks for the information and encouragement. Your name is all over the
> cmake
> infrastructure, and I would like to thank you (collectively) for how nice
> it all is.
> I'm not a huge fan of cmake, but I accept that it's the go-to for C++
> building,
> generally speaking. Some familiarity can go a long way. This is looking
> like a
> great fit for what we want to do - essentially statically link everything
> from our own
> repos of everything from the ground up - both Windows and Linux.
>
Here on my machine, I don't even need to modify my user-config.jam. b2
is just picking up the directories from the -s options I give on the
commandline. The rest is done by b2 and msvc.jam, like here (VS2022):
... libboost_atomic-vc140-mt-x64-1_83.pdb
libboost_bzip2-vc140-mt-gd-x64-1_83.lib
libboost_bzip2-vc140-mt-gd-x64-1_83.pdb
libboost_bzip2-vc140-mt-x64-1_83.lib
libboost_bzip2-vc140-mt-x64-1_83.pdb
libboost_chrono-vc140-mt-gd-x64-1_83.lib ...
Thanks Dani
-- PGP/GPG: 2CCB 3ECB 0954 5CD3 B0DB 6AA0 BA03 56A1 2C4638C5
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk