Wow, thanks, a terminating slash fixed it!
[I can't believe I didn't try that...]
Thanks very much for your help!!!
Iain.
> -----Original Message-----
> From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, July 15, 2001 8:09 PM
> To: Iain Huxley; '[EMAIL PROTECTED]'
> Subject: RE: jde-make-working-directory
>
>
> At 12:08 PM 7/13/2001 -0700, Iain Huxley wrote:
> >> for Emacs, I cannot be certain how it sets the working
> >> directory of the
> >> command that it executes. However, I suspect the NT/Emacs
> version of
> >> start-process uses the standard Windows api function, chdir,
> >> to change the
> >> working directory. This function accepts paths with forward
> >> or back slashes
> >> or both. So the style of the path should not be an issue here.
> >
> >This makes sense, but in my case, the default directory is
> not getting used
> >properly - it is set correctly - from doing a describe-variable:
> >
> >default-directory's value is
> >"c:/src/depot/JavaBrowser/Current/build"
> >Local in buffer *compilation*; global value is
> >nil
> >
> >but it does not get applied - when I do a C-c C-v C-b I get:
> > cd c:/src/depot/JavaBrowser/Current/build
> > make
> > OPUS MAKE: Nothing to make. Stop.
> > Compilation exited abnormally with code 1 at Fri Jul 13 11:50:28
> >
> >(the makefile is in this directory, but the make prog
> doesn't find it).
> >
>
> I was able to replicate this behavior. However, on further
> investigation, I
> discovered an interesting fact: it makes a difference, at
> least on Windows
> Millenimum, whether you terminate the path with a
> back/forward slash. It
> appears that only the path up to the last slash is used. For
> example, if you do
>
> M-x eval-expression (setq default-directory "c:\\foo\\bar")
>
> the working directory becomes c:\foo. You can easily confirm
> this by entering,
>
> M-x compile dir
>
> However, if you do
>
> M-x eval-expression (setq default-directory "c:\\foo\\bar\\")
>
> the working directory becomes c:\foo\bar.
>
> I found that if I terminated jde-make-working-directory with
> a slash, make
> worked. If not, make did not find the makefile. This seems to
> reproduce the
> problem you are having as it appears that you are not terminating your
> paths with slashes.
>
> - Paul
>
>
