[Boost-build] Features and passing arguments to project

From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2007-01-06 10:16:19

On 1/6/07, Vladimir Prus <ghost_at_[hidden]> wrote:
> On Thursday 04 January 2007 04:21, Felipe Magno de Almeida wrote:
>
> [snipped]

> >
> > Does anybody know how can I accomplish this?
>
> In general, "free" features are not propagated. Can you give more detailed
> example of what you're trying to do so that I can suggest some other solution?

What I'm trying to do is to let the user select which dependencies the
library would have based on some information given by him.

All that I could do until now was create a rule and importing it to
the global module.
This rule creates a new target on the current project, this is an
aliasing for the configured project.

This is a GUI library, it can use GTK/win32/qt (it is not ready yet,
this is part of a refactoring to allow use of these toolkits). But I
wanted to allow the use of one and even more than one at the same
time. So I created a manager in middle of this that redirects and
manages which "driver" (the toolkit) to use.

The syntax that I could achieve yet is:

client jamfile ---

gui.configure gui_library : static : win32 ;

exe client : $(sources) gui_library ;

There's only some problems with naming and directory builds for the
library files that I'll see if I can correct.

Do you have a better idea to solve this?
I can't use the "using" syntax because it is not a toolset nor should
be distributed with bbv2, but I wanted something just like that for
configuring it. But I also need to be able to configure something
locally to that project alone.

>
> - Volodya
>
> >
> > Thanks,
>

Thank you,
--
Felipe Magno de Almeida