From: groepaz (groepaz_at_gmx.net)
Date: 2001-12-10 22:13:11
Hello Adam, AD> But the big question is why you would want to do just that? What is there to AD> gain by using AD> #include "../a/very/long/and/troublesome/path/file.h" AD> instead of AD> #include "file.h" AD> and specifying -I../a/very/long/and/troublesome/path to ca65 or cc65? the problem is, that if i want to include the file (which includes #include "../a/very/long/and/troublesome/path/file.h") from different locations in the filesystem (for whatever reason, eg generating the main exes in the projects root and some teststuff deep inside another external built tree) ... this would only work with (to me) annoying workarounds, scattering machine-dependend paths around makefiles (i managed to not do so for a coupple of years now so why should i start with that?) etc pp i _KNOW_ that existing options and features can be used to "almost" achive what i want, and i know how to do it - i just think its limiting me in a way it shouldnt. >> however, trying relative paths in the -I line might be a working >> solution for what i want to do... didnt think of that :o) AD> The -I flag is a very good way to deal with having include files scattered AD> around. i wrote that in the mail before.... you'll run into troubles when using several files of the same name. (and yeah, i tend to do this heavily) -- Best regards, groepaz mailto:groepaz_at_gmx.net ---------------------------------------------------------------------- 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 : 2001-12-14 22:05:44 CET