Hi! On Sat, Apr 23, 2011 at 02:24:26PM +0300, Karri Kaksonen wrote: > A nice idea but it just does not work. The linker imports the eeprom66.s > always and if I specify __93C86__ then I get conflicts. This is probably because eeprom66.s contains other symbols that are referenced. So it will get linked regardless of the import statement in the linker config. I haven't tried that, but it might be possible to do something like this: eeprom66.s: .export _lynx_eeread_93c66, _lynx_eewrite_93c66 Linker config: SYMBOLS { _lynx_eeread: type = export, value = _lynx_eeread_93c66; _lynx_eewrite: type = export, value = _lynx_eewrite_93c66; } That's not as simple as your solution but probably still ok. 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 Sat Apr 23 14:09:58 2011
This archive was generated by hypermail 2.1.8 : 2011-04-23 14:10:00 CEST