From: Groepaz (groepaz_at_gmx.net)
Date: 2003-05-27 15:41:43
On Sunday 25 May 2003 23:57, Ullrich von Bassewitz wrote: > There are several methods to influence the search order. cc65 manages two > search lists: One for system header files (delimited by <>) and one for > user includes (delimited by ""). On startup, the search path list for user > includes is initialized by the current directory, while the search list for > the system includes is initialized by "include" and a precompiled value > (/usr/lib/cc65/include for linux). So by using > > #include <conio.h> > > the compiler will always find the conio.h from the system include directory > first, provided that it is in one of the directories mentioned above > (should be the default on unix systems). > > In addition to that, the compiler will add the value of the environment > variable CC65_INC (if it exists) to both search lists, as well as any path > given on the command line with -I. While additional paths are placed into > both lists, you can give them in any order. If you add the cc65 include > directory first, it will find the conio.h there. so -I always adds the given path at the start of the existing search list? also where is the CC65_INC added, at the start or the end of the search list? and in which order does all the above take place? 1) init with builtin pathes 2) add CC65_INC 3) add pathes given with -I ?! that would be the info i was looking for basically :=) > So I cannot see why this doesn't work for you. Have you used the correct > include file delimiters and tried changing the order of the -I command line > options? i'm pretty sure i tried whatever is possible :=P anyway see above, maybe it could clear up some things for me :) gpz ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2003-05-27 15:57:56 CEST