Re: [jamboost] BBv2 error message on long command line

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-12 02:45:48

Hi Johannes,

> unfortunately I'm out of office until next monday. I will be offline until
> than. Thank you very much for your patience!!!!

That you for your patience, too.

> Two questions however.
> At first is it that uncommon to have such long include pathes at all?

Nobody ever complained about this, at least. I would be a bit surprised if a 
single source file required so many includes. Maybe the problem is that 
you're adding all includes to top-level project, as opposed to specifying 
specific needed includes only for subprojects.

> Secondly, is there a generic way to name a(n) (include) path in a root jam
> file and evaluate that name in a subproject jamfile.
>
> For instance: subproject1 and subproject2 are at completly different places
> in the root-tree. root: jamfile
>
> ##
> ## Something like that
> ##
> MyPath = ./grafic/grafic/variant/ ;
>
> some subproject1: jamfile
> project some-subproject1 : requirement <incude>$(MyPath)/opengl ;
>
> some subproject2: jamfile
> project some-subproject2 : requirement <incude>$(MyPath)/opengl ;

Sure. The manual says how you can get location of the project-root:

http://www.boost.org/boost-build2/doc/html/bbv2/faq/s06.html

If you change "." in the example to "./grafic/grafic/variant", you'll get the 
behaviour you want. 

> The point I have in mind is the relative part of the path. Otherwise I'm
> always counting at which level a subproject is relative to the one which
> depends on it. Moreover, if I decide to move a subproject I have to update
> its dependencies with respect to the new location. I think I have read
> something in the documentation but as far as I remember it concerns about
> library targets.
>
> A nice weekend

Same to you!

- Volodya