Re: [Boost-users] Boost.CMake's boost_add_executable

From: Doug Gregor (dgregor_at_[hidden])
Date: 2007-08-30 13:20:34

On Aug 30, 2007, at 12:47 PM, ope wrote:

>>> Maybe I have to build all libs?
>>
>> Yes, that's it. The "wave" executable is actually built from the  
>> "tools"
>> subdirectory, so you'll either need to build from within "tools" or
>> build all libraries and tools from the top-level.
>
> $ make
> [ 60%] Built target boost_serialization-static
> [ 80%] Built target boost_wave-static
> [ 80%] Built target boost_filesystem-static
> [ 80%] Built target boost_program_options-static
> [100%] Built target wave
>
> $ ldd ../../bin/wave
>         libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7e49000)
>         libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7e24000)
>         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7e18000)
>         libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7cd0000)
>         /lib/ld-linux.so.2 (0xb7f51000)
>
> So it's static linked, well. I have to go more into the deep. I  
> adapted
> the cmake macros (I assume 1:1) for my project ....

bjam statically links wave, so we did the same thing in CMake.  
Frankly, I'd prefer that we used dynamic linking wherever possible,  
because it would save a *lot* of space.

        - Doug