Re: [cc65] --create-dep for ca65?

On 2010-05-02, at 22:15, Oliver Schmidt wrote:

>>> - '--create-full-deps' isn't necessary
>>> 
>>> and turns the Makefile most
>>> certainly useless for Windows users.
> 
>> Because of the absolute paths, I guess?
> 
> You're right. Path with colons just work in GNU Makefiles.

Okay, after a few seconds of head-scratching - you mean they _don't_ work...

>> I might sound ignorant so have mercy (I ditched my last Windows system some time in late 2002) but doesn't cygwin (that was what I recall I used to bring some common unix tools, including make itself, to Windows back then) take care of that? Doesn't it change the access from C:\dir0\dir1\file0 to something like /drives/c/dir0/dir1/file0 ?
> 
> You're right. But unfortunately this makes things in this scenario
> even worse. cc65 isn't a Cygwin program and therefore writes "native"
> Windows paths into the .d files.

Hm, I have no Windows around (are you running Windows there?) to check that but quoting Uz from his last message:

"[...] when checking for a path separator, the software checks for '/' or '\', and it uses '/' when inserting one."

Still - this might be only when he specifically needs to deal with constructing the paths himself


> Just avoiding that very small overhead for sure wouldn't have made Uz
> change the code. Rather it was the option to avoid the weird hacks
> necessary today on Windows / Cygwin.

Does this mean that the "previous" --create-dep, which was in fact taking the system includes into account was actually giving those headaches?


----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.