From: Lally Singh (lally.singh_at_[hidden])
Date: 2006-06-25 16:08:21
It's helping, and I'm very close!
The new Jamfile.v2:
using gcc ;
exe mfront :
: <include>. <include>/usr/local/src/boost
Only thing that fails now is an unknown flag given to ld:
/usr/bin/ld: unknown flag: --start-group
collect2: ld returned 1 exit status
"g++" -o "bin/gcc/debug/mfront" -Wl,--start-group
"bin/gcc/debug/output.o" "bin/gcc/debug/main.o" "bin/gcc/debug/map.o"
...failed gcc.link bin/gcc/debug/mfront...
...failed updating 1 target...
...updated 7 targets...
Perhaps I need to define a different toolchain? (MacOSX 10.4.6)
Also, one slightly-related question: is there a way to call the
compiler with another name (e.g. call "gfilt" instead of "g++")? I'd
like to use STLFilt.
Thanks for your help!
On 6/25/06, Reece Dunn <msclrhd_at_[hidden]> wrote:
> Lally Singh wrote:
> > Hey all, simple question (please redirect me if this is the wrong place):
> > I've got a project that needs linking with some boost libraries, and I
> > don't know how to tell bjam to do it.
> > The Jamfile ends up in the files getting compiled, but the libraries
> > aren't linked in, causing the build to fail.
> > My Jamfile:
> > exe mfront : ./driver/driver.cpp ./main.cpp ./parser/generator.cpp :
> > <lib>filesystem <lib>wave ;
> You'd be better switching over to Boost Build V2 as V1 is being phased
> out. In V2, this would be:
> exe mfront
> ./driver/driver.cpp ./main.cpp ./parser/generator.cpp
> This might work for V1: i.e. replacing <lib>wave with either
> <lib>boost//wave or <lib>$(BOOST_ROOT)//wave, but I don't
> know enough about V1 to confirm that this is correct.
> - Reece
> Try Live.com - your fast, personalized homepage with all the things you care about in one place.
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk