On Dienstag 16 März 2010, you wrote: > On 2010-03-16, at 19:01, Ullrich von Bassewitz wrote: > > [...] > > > The only real solution for that problem is to replace the module > > that contains > > write by one that exports the same identifier and functionality. > > Which in fact > > means another, ide64 specific library. > > I am not sure if anybody reads that but I'll try once more: if there > is a clear recipe on how to easily achieve the desired results by > simply recompiling/relinking the program with different parameters, > but without any changes to the code, then automating the updates of > IDE64 augmented, specific library (or any similar for that matter) > should not be a really hard task. Or would it? Or am I completely > wrong here? i simply do it like this.... in my makefile i pull a copy of the current compiled c64.lib from my installed cc65. then i extract the lib into a temporary directory. now my project-specific replacement files (which are - surprise, usually read/write and friends =P) will be compiled, the generated objects copied to the temporary directory, and finally a new project specific c64.lib is created, which then can be used to link against other files in the project. all that is very straightforward, easy to achive, and has (at least not to me) obvious drawbacks. its all fully automatic too :) -- http://www.hitmen-console.org http://magicdisk.untergrund.net http://www.pokefinder.org http://ftp.pokefinder.org Man kann garnicht so dumm denken wie es manchmal kommt. ---------------------------------------------------------------------- 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 Mar 16 20:00:18 2010
This archive was generated by hypermail 2.1.8 : 2010-03-16 20:00:21 CET