From: groepaz (groepaz_at_gmx.net)
Date: 2002-11-21 00:56:07
Hello Ullrich, UvB> Wait... I forgot, that I did this before and that there is an easy solution:-) UvB> Just place the code that has to go into low memory into a special segment UvB> (which is always the same, regardless of the module). Then place this segment UvB> as first segment into the memory area using the linker config. In fact, this UvB> approach does exactly the same as your suggestion of a "place at the UvB> beginning" linker command. The C128 uses this solution, since the interrupt UvB> handler for the RS232 module has to go into low memory. UvB> There is still the problem that the segment can exceed the non banked memory, UvB> but it is a solution that works with the current capabilities. sounds ok...and doesnt require much work ;=D hehe UvB> Second, it is always better to have the files in /usr/bin managed by a package UvB> manager. So I'm usually building RPMs when I want to have a new compiler UvB> version installed systemwide. With the new fresh snapshot RPMs built each UvB> night, this will become even easier in the future:-) it will remove the need of such toplevel for me entirely i guess ;=P UvB> So this is neither complicated nor boring. Besides that, a top level UvB> "makefile" could just be a shell script that does UvB> make -C src -f make/gcc.mak UvB> make -C libsrc -s well its ofcoz like that :) (plus copying to /usr/bin.... as former windows user i have no worries with doing things i shouldnt when it comes to system directories hahaha :o)) -- Best regards, groepaz mailto:groepaz_at_gmx.net ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2002-11-21 00:56:14 CET