Share

Framewave

Tracker: Feature Requests

3 Be able to link against system boost library - ID: 1962491
Last Update: Comment added ( nobody )

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.


Orion Poplawski ( opoplawski ) - 2008-05-12 16:22

3

Open

None

Nobody/Anonymous

None

1.1

Public


Comments ( 2 )




Date: 2008-07-25 06:12
Sender: nobody

Logged In: NO

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


Date: 2008-05-29 04:50
Sender: pksvProject Admin


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


Log in to comment.

Attached File ( 1 )

Filename Description Download
framewave-1.1-boost.patch Remove local boost compilation Download

Changes ( 3 )

Field Old Value Date By
artifact_group_id None 2008-05-29 04:50 pksv
priority 5 2008-05-29 04:50 pksv
File Added 277537: framewave-1.1-boost.patch 2008-05-12 16:22 opoplawski