Re: is bjam 3.1.10 and mingw broken?

From: andrewjmcd (andrewjmcd_at_[hidden])
Date: 2004-10-12 01:59:21

--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> andrewjmcd wrote:
> 
> 
> It is. Guys, maybe we should not be putting any boost-jam releases on 
> sourceforge unless they are known to work with V2? Or were there any 
> V1-related fixes in bjam?
> 

that would be great! And consistent with a top class tool like bjam :>

> > current is a nightly build then?
> 
> Yes.
> 

okey dokey

> > > > How come bjam is unable to use the current directory for the
library?
> > >
> > > This has nothing to do with bjam. If the linker doesn't find the
> >
> > library
> >
> > > located in the current directory, you need to add that directory
to the
> > > search path.
> > >
> > > - Volodya
> >
> 
> > I put everything in the same directory to avoid that!
> 
> If gcc does not look for libraries in the current directory, what
can V2 do? 
> 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>"."
.
.
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
;
_________________

Andrew