build-project in its own directory

[Anatoli Sakhnik-2]

Hi there!

I have plenty of executables each residing in its own directory.
They're built from the Jamroot using the rule build-project. Every
executable somehow uses the macro __FILE__ to enrich log messages.

Now, when a project is built in its own directory separately, the
macro __FILE__ contains the name of the file relative to the project's
Jamfile. But when building the whole suite, the macro contains the
whole path from the Jamroot.

Is there a way to let every project be built in its own directory when
building the whole suite?

Anatoli Sakhnik
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Steven Watanabe-4]

AMDG

Anatoli Sakhnik wrote:

> I have plenty of executables each residing in its own directory.
> They're built from the Jamroot using the rule build-project. Every
> executable somehow uses the macro __FILE__ to enrich log messages.
>
> Now, when a project is built in its own directory separately, the
> macro __FILE__ contains the name of the file relative to the project's
> Jamfile. But when building the whole suite, the macro contains the
> whole path from the Jamroot.
>
> Is there a way to let every project be built in its own directory when
> building the whole suite?
>  

No there isn't.  All targets are built from the current working directory.
I recall seeing an open ticket for this...

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build