Hi! On Fri, Apr 23, 2010 at 12:47:03PM +0200, Oliver Schmidt wrote: > - The "it's in the path" default typically doesn't get you far as the > tools don't find their headers and libraries without environment > variables set. On Windows this has always been this way and if I > understood a recent discussion on this list right than this is now > true on Unix as well. Not really. The precompiled packages for *nix don't need environment variables, since all necessary paths are built into the executables. This is especially true for all precompiled (binary) packages - they work right out of the box. It is not true in the following cases: * Someone built the binaries but didn't adjust the install path when doing so. I would consider this an error in the build process. * The binaries are used from within a development tree of cc65. In this case it's better to specify explicit search paths on the command line instead of relying on environment variables. So actually CC65_HOME (and the other variables) are more a feature for DOS derived operating systems. Most Unix software has at least some compiled in paths and cc65 is no exception. 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 Fri Apr 23 14:08:51 2010
This archive was generated by hypermail 2.1.8 : 2010-04-23 14:08:54 CEST