Re: [cc65] Relative paths during compilation

Hi Uz,

>> Is this a bug, or feature (will be in future versions) that files
>> are included relative to the 'current directory', not to the
>> directory where the includer resides. This behavior is for asm and C
>> files (.incbin, #include).
>> My project is getting bigger and I would like to split sources to
>> different directories, but now I cannot do #include
>> "..\upper_dir\otherfile.h", because it depends on the directory,
>> where the compilation was started (by cl65).

The _current_ behaviour of cc65 and ca65 seems to be different...

If I have a C file foo.c with #include "foo.h" and compile it from the
parent directory as src/foo.c then I can have the compiler find foo.h
by adding the option -I src.

If however I have an asm file bar.s with .include "bar.inc" and
assemble it from the parent directory as src/bar.s then I _can't_ have
the assembler find bar.inc by adding -I src.

Do I miss some point here? Is this intended this way?

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