On Sat, Sep 01, 2012 at 11:03:08AM +0100, Jeremy Henty wrote: > > Armin K. wrote: > > > > > I'd also like to add that there are two targets with ./b2 tool. > > > > stage target will build the package and not install it, and install > > target will build the package if not already built and install it. > > Minor gotcha - if you split the build and the install this way and you > want "link=shared" then you must pass it to both "./b2" and "./b2 > install" otherwise the install builds the static libraries. (Verified > with boost_1_51_0 .) I don't what happens if you build with "./b2 > stage" instead of just "./b2"; I assume the results would be the same > but I haven't checked. > > Regards, > > Jeremy Henty
I have to disagree with Jeremy. I too have not explored the stage target, but doing what is in effect a DESTDIR install, all the libs except libboost_exception and libboost_test_exec_monitor are shared. In my experience those two are only ever built as static. Since my eyesight has proved problematic in this, I'll paste the commands I used : ./bootstrap.sh --prefix=/scratch/ken/BOOSTmultishared/usr ./b2 -j3 2>&1 | tee buildlog ./b2 install threading=multi link=shared 2>&1 | tee instlog ls -lR ../BOOSTmultishared/usr/lib/*.a ls ../BOOSTmultishared/usr/lib/*.so* | wc -l That last one reports 52, i.e. 26 .so symlinks, and 26 actual .so.1.51.0 shared libraries. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
