Re: [jamboost] [V2 msvc] using msv-toolset

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-02-18 07:40:25

Jürgen Hunold wrote:

> > The tutorial section in boost_build_v2.html describes it. Or have I
> > misunderstood you?
>
> Well, yes,sorry ;-) I was wondering how the path must be specified.
> If I use Win32 backslash, weird things happen.
> I get -I"E:Librarieslix" as command argument.
> If I use slash as path specifier, I get -I"../E:/Libraries/libx" on
> the command line.
> Seems to be an unsupported or unimplemented feature, right ?

Something like that. It's assumed that all paths specified by the user are in 
canonical form. In this case, you should specify

<include>/E:/Libraries/libx

(the syntax is ugly and I did not realize we have to use it on user level. 
Guess we can improve this situation).

> > Also, could you clarify the question about LIBX_ROOT. Do you mean
> > using it to tell where the library is located and do 'use-project'
> > on that location?
>
> Yes. I'd like to add something like <include>$(LIBX_ROOT)/include
> or use-project /libX : $(LIBX_ROOT)/src to the Jamfile.
> That means resolving of environment variables.

They are resolved :-) All environmental variables become
jam variables in global scope. The only problem is that everything in
V2 is in modules, so you'd have to use

local r = [ modules.peek : LIBX_ROOT ] ;

to get access to them.

> > > 2) The compile detection fails. I'd guess this is due to the fact
> > > that I'm using a german installation, where programs live in
> > > "C:\Programme" instead of "C:\Program Files".
> > > Any ideas about that ?
> >
> > I'm pretty sure Rene had the same problem with "build.bat" script.
> > We might look there for an answer.
>
> Ah, I see. I'm running vcvars32.bat while starting up the cygwin-bash.
> Could this cause problems ?

I don't know. 
BTW, do you have "ProgramFiles" variable in environment. What's its value?

- Volodya