#15 Be able to link against system boost library

1.1
open
nobody
None
3
2008-05-29
2008-05-12
No

I had to apply the attached patch plus the following:

sed -i -e 's/-lpthread/-lboost_thread-mt/' BuildTools/buildscripts/fwflags_gcc.py

to be able to compile against the system boost library. It would be nice if this could be a build option.

Also, I end up with:

framewave.i386: W: unused-direct-shlib-dependency /usr/lib/libfwImage.so.1.1.0 /usr/lib/libboost_thread-mt.so.3
framewave.i386: W: unused-direct-shlib-dependency /usr/lib/libfwVideo.so.1.1.0 /usr/lib/libboost_thread-mt.so.3
framewave.i386: W: unused-direct-shlib-dependency /usr/lib/libfwJPEG.so.1.1.0 /usr/lib/libboost_thread-mt.so.3
framewave.i386: W: unused-direct-shlib-dependency /usr/lib/libfwSignal.so.1.1.0/usr/lib/libboost_thread-mt.so.3

because all of these get linked against libboost_thread-mt (or pthread without the change) but don't need to be. LDFlags should be able to different for different library targets.

Discussion

  • pksv

    pksv - 2008-05-29

    Logged In: YES
    user_id=1953312
    Originator: NO

    We will work to simply the build system and make it easy to specify the compile and link flags. Following our discussion and given you have a work around for now, we will take this up immediately after the current (version 1.2) release cycle, which is due end of July . Hence lowering the priority for this release

     
  • pksv

    pksv - 2008-05-29
    • milestone: --> 1.1
    • priority: 5 --> 3
     
  • Nobody/Anonymous

    Logged In: NO

    Use the command line option thread=systemboost to compile using the system boost library.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks