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, b and c, but not the long filename.
SHELL=cmd.exe
q=$(1)$(1)$(1)$(1)$(1)
long=$(call q,01234567890123456789)
ifeq ($(findstring $(long),$(shell cd)),)
default:
-mkdir $(long)
$(MAKE) -C $(long) -f ..\Makefile
else
src="">
$(info $(shell mkdir ..\src) $(shell mkdir $(src)))
files=a b c 0123456789012345678901234567890123456789
$(info $(foreach f,$(files),$(shell echo > $(src)/$(f))))
VPATH=$(src)
default: $(files)
@echo ok
endif
- Any known problems with relative paths in VPATH on Windows?, Erik Carstensen, 2013/05/06
- Re: Any known problems with relative paths in VPATH on Windows?, Erik Carstensen, 2013/05/06
- Re: Any known problems with relative paths in VPATH on Windows?, Eli Zaretskii, 2013/05/06
- Re: Any known problems with relative paths in VPATH on Windows?,
Erik Carstensen <=
- RE: Any known problems with relative paths in VPATH on Windows?, Duane Campbell, 2013/05/06
- Re: Any known problems with relative paths in VPATH on Windows?, Eli Zaretskii, 2013/05/06
- Re: Any known problems with relative paths in VPATH on Windows?, Erik Carstensen, 2013/05/06
- Re: Any known problems with relative paths in VPATH on Windows?, Eli Zaretskii, 2013/05/07
- RE: Any known problems with relative paths in VPATH on Windows?, Duane Campbell, 2013/05/07
- Re: Any known problems with relative paths in VPATH on Windows?, Erik Carstensen, 2013/05/07
- Re: Any known problems with relative paths in VPATH on Windows?, Erik Carstensen, 2013/05/07