Re: Spaces in file names!!

[Mark Grosen]

Yes, this can be a problem. Two approaches I have used to solve it:

* Include a file that defines all the locations of your tools as make
variables. This can be done by machine name or some other criteria
that "knows" actual locations of the tools.
* Define the variables using an external utility that maps LFN to SFN
     MSVC = $(shell long2short "c:/program files/visual studio")

     CC = $(MSVC)/bin/cl.exe

Mark

--- Greg Chicares <address@hidden> wrote:
> Mark Grosen wrote:
> > 
> [Zhang Zhenhua wrote about a problem using a path
> with embedded spaces, and I suggested quoting it]
> > 
> > You can also use the Short Filename (SFN) format of the path. Use
> dir
> > /x in a command (cmd) window to see the SFN. For example, your
> > example would probably be something like:
> > 
> > SDCC = c:\mywork~1\compiler\bin\sdcc.exe
> 
> I've tried that approach too. Here's a problem
> with it. Create directories like
>   My Work
>   My Work 20021106
>   My Work test version
> and record the 'short' paths, like mywork~[1-3] .
> Then create them on a different machine in a
> different order, or erase and recreate them
> on the same machine in a different order. They
> now map to different 'short' paths.
> 
> 
> _______________________________________________
> Make-w32 mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/make-w32