Re: [Boost-build] Won't build - Hello example fails

Subject: Re: [Boost-build] Won't build - Hello example fails
From: Christopher Pisz (cpisz_at_[hidden])
Date: 2011-03-15 14:48:42

On 3/14/2011 1:26 PM, Christopher Pisz wrote:
> On 3/14/2011 12:45 PM, Vladimir Prus wrote:
>> On Monday, March 14, 2011 19:57:03 Christopher Pisz wrote:
>>> It is my 4th day on a new job. They are using boost and evidently build
>>> it into a library, thus my question to this group.
>>>
>>> Everyone else seems to build without a hitch, but for some reason mine
>>> fails. I tracked it down to a custom build action in one of the Visual
>>> Studio 2008 projects, that is part of the solution I am working on, that
>>> looks like this:
>>>
>>> cd ..\boost
>>> SET PATH=$(PATH);..\bjam
>>> bjam.exe --stagedir=./ --with-thread toolset=msvc-9.0 link=static
>>> threading=multi runtime-link=shared variant=debug stage
>>> bjam.exe --stagedir=./ --with-date_time toolset=msvc-9.0 link=static
>>> threading=multi runtime-link=shared variant=debug stage
>>> bjam.exe --stagedir=./ --with-system toolset=msvc-9.0 link=static
>>> threading=multi runtime-link=shared variant=debug stage
>>> bjam.exe --stagedir=./ --with-regex toolset=msvc-9.0 link=static
>>> threading=multi runtime-link=shared variant=debug stage
>>> bjam.exe --stagedir=./ --with-program_options toolset=msvc-9.0
>>> link=static threading=multi runtime-link=shared variant=debug stage
>>> bjam.exe --stagedir=./ --with-filesystem toolset=msvc-9.0 link=static
>>> threading=multi runtime-link=shared variant=debug stage
>>>
>>>
>>> I tried manually entering the commands at the command line and the very
>>> first call to bjam.exe fails
>>>
>>> Additionally, I started reading the Boost.Build manual that came with
>>> their version of boost and the same error occurs when I try the "hello"
>>> example.
>>>
>>> I can't figure out how or where from it is getting the path
>>> 'C:\DOCUME~1\cpisz\Local', but obviously it is not interpreting the
>>> space in "local settings" as part of the path. When I look at the build
>>> log on my peer's machines, they have a path of the
>>> "C:\DOCUME~1\user\LOCALSE~1" type. They have the ~1 and double quotes
>>> while I don't. Where is this path coming from?
>>>
>>>
>>>
>>> My output looks like this:
>>>
>>> C:\Perforce\TSS\vendor\boost\tools\build\v2\example\hello>bjam
>>> ...found 11 targets...
>>> ...updating 7 targets...
>>> common.mkdir bin
>>> 'C:\DOCUME~1\cpisz\Local' is not recognized as an internal or external
>>> command, operable program or batch file.
>>>
>>> if not exist "bin\\" mkdir "bin"
>>
>> What is the value of TMP and TEMP environment varibles?
>>
>> - Volodya
>>
>
>
> Both are set to C:\Windows\Temp
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>

I found today that everyone in the office has "user variables", which 
are indeed set to %USRPROFILE%\Local Settings\Temp
I changed mine to C:\Windows\Temp and it built. However, I am unclear 
why I have the need to change mine, yet none of my peers have this 
problem. It seems the boost build programs can't inturpret the space 
between 'local' and 'settings' on my machine, but it can on everyone else.