Hi, I have a small question about linking in C-library stuff. We are currently working to publish a Multicart 2006 for the Atari Lynx and Carl Forhan got a great idea to increase the 128 byte EEPROM usually found on Lynx carts to 2K. The idea is that you could then compile your own small applications and transfer them to the EEPROM. My idea is to create a new link target EEPROM.bin that would contain the code, data and rodata segments of the user created game only. When I would like to run my EEPROM segment I would read in the RAM-segment containing all the C-library code, drivers etc. from the cart and on top of this I then load the EEPROM-segment and jump to the start of code there. This means that I need to link my EEPROM code with the original cart code produced earlier. My question is: Is it possible to force the entire C-library into my RAM-segment somehow so that future EEPROM-based gamed would not need additions to the resident RAM-segment? I thought of creating a dummy application that would use all kind of C-command and library calls just to force the routines onto the cart. But perhaps there is some neat way to tell the linker to include everything? Or perhaps "everything" is too much for the limited ram space. -- Karri ---------------------------------------------------------------------- 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 Feb 14 10:20:18 2006
This archive was generated by hypermail 2.1.8 : 2006-02-14 10:20:21 CET