Re: [cc65] Relative paths during compilation

From: Ullrich von Bassewitz <uz1musoftware.de>
Date: 2010-01-16 14:29:54
On Sat, Jan 16, 2010 at 11:02:32AM +0100, Markus Stehr wrote:
> Shouldnt it be that #include "foo.h" is from the current directoy and
> #include <bar.h> is from "$COMPILER_DIR/include" (or /usr/include in
> gcc's case...)?

That is a common implementation, but not defined anywhere in the standard. The
standard doesn't know anything about "include directories" and it doesn't even
require that standard includes reside physically somewhere.

But the actual question was, how "current directory" is defined. Is it the
current directory where the compiler was started? Or the directory where the
file lives, that contains the include statement?

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Sat Jan 16 14:30:00 2010

This archive was generated by hypermail 2.1.8 : 2010-01-16 14:30:02 CET