On Tue, Sep 14, 2004 at 11:46:28AM +0300, Karri Kaksonen wrote: > What about other required programs for the Lynx target? That depends mostly on the copyright/license. I would prefer not to include any code in the package with other licenses than the new cc65 one (which is in fact the zlib license). If these programs have another license, it does not mean that they're unusable, but I would prefer having them in separate package in another location. > Finally I need to create a Lynx filesystem. The filesystem is extremely > simple. Just several fileentry structs in a row: [...] > Could the linker produce this right away somehow or do we need to write a > real program to deal with this? There is a program called lynxer.c that > people are using today. But it is very picky about where it is run from. The linker should be able to handle that if you move the fileentry structs into a separate segment that comes first in the memory area. > Could these external programs be put in contrib/lynx in the cc65.org > archives? Or what is the way you usually deal with this kind of software? Besides the license it would be nice if these programs integrate smoothly into the existing tools (if the license permits that, of course). For the sprite packer for example, it would be great to have it included into the cl65 frontend utility. Regards Uz P.S.: Your other mail to the list bounced because of too much quoted material. I would suggest stripping it down and reposting it to the list. -- 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 Sep 14 13:14:38 2004
This archive was generated by hypermail 2.1.8 : 2004-09-14 13:14:47 CEST