Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-02-05 07:07:19

> >I think
> >
> >
> >
> >gets
> That is cool :). The only drawback is, I'd need to add a lib entry for all
> the PlatformSDK libs :(. Or is there a way to templatize it, e.g.
> forall $lib : <match>*.lib <search>$path.psdk
> {
> lib $lib : : <file>$lib.lib ;
> }

It probably can be done via some more explicit jam code. OTOH, I'm really
wondering if we should open to user a way to get searched library *without*
declaring a target.

The original idea was that you can write "your_cool_lib" and don't care if the
lib if regularly built, searched or just lying here as a .lib file.

But for many cases, this flexibility is not necessary. I think that even now,
you can use

exe a : a.cpp : <find-shared-library>a.lib ;

except that the feature is not documented. What do people think?

> > > [3] Is it possible to perform specific actions on a target? E.g. move
> > > an exe to a specific directory once built?
> >
> > exe a : a.cpp ;
> > stage dist : a ;
> I'm aware of this action. The problem is that it creates a subdirectory
> called dist then reinvokes the link action to build the exe to the dist
> directory. This isn't bad, and can be useful in some situations. I have a
> bin folder that I put some programs that I build into so I can invoke them.
> This is a simple move command, e.g.
> move : a : $path.mybin ;

Such a rule can be easily written I guess. I just not sure it's very needed,
especially if ... (see below)...

> > exe hello : hello.cpp ;
> > notfile done : echo "build complete" : hello ;
> >
> >But probably you have something else in mind...
> This is similar to what I would like to do, and the facility would allow
> for better custom builds.

... as this should allow to do manual things. The feature is sheduled for M11,
so this is not so distant future.

- Volodya


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at