On Fri, Sep 25, 2009 at 10:17:37AM +0200, Groepaz wrote: > i dont quite understand what the problem is with linking additional libraries > though :) except that it would require splitting the lib into several libs > and not put everything into one - which IMHO isnt the optimal approach, as it > is kinda limiting. cc65 cannot be everything for everyone. Trying to integrate each and every user project into cc65 will make it unmaintainable in the long run. Once stuff is integrated into cc65, I'm the one who gets the complaints and will have to maintain it. As an example, see the discussion about the master makefile. I never wanted this thing, but people complain here if it doesn't work, and I have to spend my time discussing it and explain why it broke. My suggestions for projects like this is: Make it a contrib project that compiles into a few replacement modues. As an option, offer a command file that takes the cc65 standard library for the platform and generates a copy by replacing the modules in question. If dozens of people start using the contrib project, there is time enough to check if an integration makes sense. 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 Sep 25 12:05:07 2009
This archive was generated by hypermail 2.1.8 : 2009-09-25 12:05:10 CEST