From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-10-12 02:05:46
> > Yes, we can add "." to the search patch automatically, but if gcc
> don't do
> > it, there might be a reason?
> but that is my point gcc is automatically able to realize that it has
> been given a dll and pass it on to the linker.
> C:\gcc -o foo.exe foo.c bar.dll
> works, so it does do a -L"."
> And you provided that answer .. got to specify
> lib bar : : <name>bar <search>"."
Heh... that's different, with
lib bar : : <name>bar <search>"." ;
The gcc command line will be
gcc ........ foo.c -lbar
If you know the exact location for the library, just write
lib bar : : <file>bar.dll ;
alias bar : bar.dll ;
and this should work.
> Change of topic.
> At the time I was making a python module and was curious how the <dll>
> qualifier in pyste tutorial example was defined.
> repeated here for clarity....
> # Hello World Example from the tutorial
> # [Joel de Guzman 10/9/2002]
> # Specify our location in the boost project hierarchy
> subproject libs/python/example/tutorial ;
> # Include definitions needed for Python modules
> import python ;
> extension hello # Declare a Python extension
> called hello
> : hello.cpp # source
> <dll>../../build/boost_python # dependencies
That's V1 syntax. V2 does not need <dll> prefix.
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