On Tue, May 7, 2013 at 6:51 PM, Duane Campbell wrote:
> Erik, are you familiar with subst command?
>
> If not, you might find it handy as a work-around for windows limitations:
>subst someUnusedDriveLetter: c:\very-long-src-dir
> like
>subst S: c:\very-long-src-dir
> Then use S:\ in-place
On Tue, May 7, 2013 at 6:36 PM, Eli Zaretskii wrote:
> The easiest way around the problem is this:
>
> VPATH = $(abspath ..\very-long-build-dir);$(abspath ..\yet-another-one)
>
>
I cannot do that, because very-long-src-dir contains spaces.
What I have done instead is to detect this condition
7
To: Erik Carstensen
Cc: Duane Campbell; make-w32@gnu.org
Subject: Re: Any known problems with relative paths in VPATH on Windows?
> Date: Mon, 6 May 2013 21:55:11 +0200
> From: Erik Carstensen
> Cc: Duane Campbell , make-w32@gnu.org
>
> On Mon, May 6, 2013 at 9:48 PM, Eli Zaretskii
> Date: Mon, 6 May 2013 21:55:11 +0200
> From: Erik Carstensen
> Cc: Duane Campbell , make-w32@gnu.org
>
> On Mon, May 6, 2013 at 9:48 PM, Eli Zaretskii wrote:
>
>
> > Maybe c:\very-long-src-dir\..\very-long-build-dir together exceeded
> > 260 characters?
>
>
> No, make can find 'c:\very-lon
On Mon, May 6, 2013 at 9:48 PM, Eli Zaretskii wrote:
> Maybe c:\very-long-src-dir\..\very-long-build-dir together exceeded
> 260 characters?
No, make can find 'c:\very-long-src-dir\..\very-long-build-dir\a', but not
'c:\very-long-src-dir\..\very-long-build-dir\very-long-filename'.
On the symp
> From: Duane Campbell
> CC: "make-w32@gnu.org" , Duane Campbell
>
> Date: Mon, 6 May 2013 11:55:28 -0700
>
> Windows has limits on path length, approximately (as I don't remember exactly
> off-hand):
> 256 chars total in dir or file path
> 128 chars in each element in dir or file pat
g] On Behalf Of Erik
Carstensen
Sent: 2013-05-06 Monday 11:51
To: Eli Zaretskii
Cc: make-w32@gnu.org
Subject: Re: Any known problems with relative paths in VPATH on Windows?
Here is a makefile that reproduces it. The makefile is a bit hacky (creates a
directory and calls itself from it); this is
Here is a makefile that reproduces it. The makefile is a bit hacky (creates
a directory and calls itself from it); this is just to be able to reproduce
it in a single makefile. The 'else' clause is the relevant one. If you put
the makefile in a reasonable path (I used c:\cygwin\tmp), it will find a
> Date: Mon, 6 May 2013 15:45:43 +0200
> From: Erik Carstensen
>
> I found the problem, there seems to be a limit in VPATH resolution of
> around 256 characters, where ..\ entries in the path are not collapsed. In
> my example, I ran make from c:\path\very-long-build-dir, and had
> ..\very-long-s
On Mon, May 6, 2013 at 10:41 AM, Erik Carstensen
wrote:
> Hi,
>
> Are there any known problems or caveats with having relative paths with
> ..\ in VPATH on Windows?
>
I found the problem, there seems to be a limit in VPATH resolution of
around 256 characters, where ..\ entries in the path are n
Hi,
Are there any known problems or caveats with having relative paths with ..\
in VPATH on Windows?
I'm getting some strange errors: I have a directory on the form
..\..\..\..\foo\bar on VPATH, where there are two .c files. make finds one,
but not the other, via VPATH, and make -d gives me no cl
11 matches
Mail list logo
