Re: [Boost-build] Build error when adding Boost libraries to own projects

Subject: Re: [Boost-build] Build error when adding Boost libraries to own projects
From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2012-08-07 09:57:00

   Hi.

>    Slight correction - you can not use the project-id defined by the
> use-project rule as the boost-system project module already defines its
> own project id boost/system and so the id specified with the use-project
> rule seems to be ignored (hmmmm - also something to look into... this
> should perhaps be added as an additional project id for the same project
> or at least reported as an error...).

   Just looked into this and it seems you can use the project-id defined 
by the use-project rule after all, it is just that such project-ids need 
to start with a slash ('/').

   So the following two examples should be equivalent:

> use-project /xxx : my/remote/project ;
> exe aaa : my/remote/project//aaa_obj ;

   and

> use-project /xxx : my/remote/project ;
> exe aaa : /xxx//aaa_obj ;

   Hope this helps.

   Best regards,
     Jurko Gospodnetić

P.S.
   I'll take a look now to see if we can issue some better diagnostic 
message if a 'non-rooted' project-id is used here instead of the current 
'could not find project' error.