On Tue, Jan 26, 2010 at 04:47:12PM +0100, Christian Krüger wrote: > What about a basic support in the linker which allows a setting from where the runtime / stdlibs > are 'pulled'? The SMC branch could be officially unsupported then but would allow an easy switch > for my 'private' use? There is no need for such a setting, because it's already there. You can explicitly name the library on the command line including the path. Or define your own search path, so your library is found. What you can do is to create your own library containing just replacement modules for existing ones. Then write a small script that does ar65 x replacement.lib ar65 d platform.lib *.o ar65 a platform.lib *.o This will unpack your library, remove all object files in the replacement library from the standard platform library (for example c64.lib) and then add the replacement modules instead. The result is a platform library with your replacment modules that can be linked to an application instead of the standard library. If you pass the replacement library plus the script to other people, they're able to do the same. 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 Tue Jan 26 17:06:29 2010
This archive was generated by hypermail 2.1.8 : 2010-01-26 17:06:31 CET