Hi! On Mon, Oct 22, 2012 at 12:27:59PM +0200, Uffe Jakobsen wrote: > path *IF* the compiled "compiled in directory paths" exists - and > there is nothing that he/she can do to get around it as far as I can > see. There is an easy way to have exactly the search paths you want: Just use --forget-inc-paths when calling any of the tools. This will remove all paths including the builtin ones from the search list. Then use -I to setup your own search list. > A multi-user development system running unix distribution X that has > CC65 installed from the distribution package repository. > > The CC65 installation fulfills most of the developers needs but the > CC65 package is rather old and a few of the developers need one or > more new versions of CC65 installed on the that system. > > The problem here is that the manually installed CC65 packages still > will find and use the old includes, libs etc that belong to the CC65 > installed from the package repo. Because of the current priority the > packages have a hard time co-existing. Please note that I'm developing cc65 under Linux and this is exactly the scenario I'm living with every day:-) I have a stable version of cc65 installed and I'm using one or more development versions in several directories. The library build system does even have --forget-inc-paths sprinkled everywhere over the makefiles because otherwise it wouldn't be possible to build a development version on a system that has a stable version installed. 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 Mon Oct 22 15:07:12 2012
This archive was generated by hypermail 2.1.8 : 2012-10-22 15:07:16 CEST