Windows bjam and 8.3 paths

On my machine, %TEMP% expands to
C:DOCUME~1daveLOCALS~1Temp
%TEMP%build seems like a convenient thing to point my
--build-dir at,
but when I do that, as BB tries to execute its MkDir rule,
the shell
complains that neither C:DOCUME~1daveLOCALS~1Temp nor
C:DOCUME~1daveLOCALS~1 nor C:DOCUME~1dave nor
C:DOCUME~1 exist.
Is there something we can do to get bjam to play nice with
the short
form of paths?  Come to think of it, is there some way we
could
exploit 8.3 paths to get around the line length issue?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

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

David Abrahams wrote:
> On my machine, %TEMP% expands to
C:DOCUME~1daveLOCALS~1Temp
> %TEMP%build seems like a convenient thing to point my
--build-dir at,
> but when I do that, as BB tries to execute its MkDir
rule, the shell
> complains that neither C:DOCUME~1daveLOCALS~1Temp
nor
> C:DOCUME~1daveLOCALS~1 nor C:DOCUME~1dave nor
C:DOCUME~1 exist.
> Is there something we can do to get bjam to play nice
with the short
> form of paths?  Come to think of it, is there some way
we could
> exploit 8.3 paths to get around the line length issue?

anybody thinking about this should know that they are not
always 
available as it is possible to disable the generation of
these names 
in the registry (for performance reasons).

Kevin

-- 
| Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this
     |
| Senior Technology                     | My employer for
certain |
| And Network Systems Architect         | Not even myself   
     |
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

David Abrahams wrote:
> On my machine, %TEMP% expands to
C:DOCUME~1daveLOCALS~1Temp
> %TEMP%build seems like a convenient thing to point my
--build-dir at,
> but when I do that, as BB tries to execute its MkDir
rule, the shell
> complains that neither C:DOCUME~1daveLOCALS~1Temp
nor
> C:DOCUME~1daveLOCALS~1 nor C:DOCUME~1dave nor
C:DOCUME~1 exist.
> Is there something we can do to get bjam to play nice
with the short
> form of paths?  Come to think of it, is there some way
we could
> exploit 8.3 paths to get around the line length issue?

anybody thinking about this should know that they are not
always 
available as it is possible to disable the generation of
these names 
in the registry (for performance reasons).

Kevin

-- 
| Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this
     |
| Senior Technology                     | My employer for
certain |
| And Network Systems Architect         | Not even myself   
     |

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