Hi Uz, >> .include >> .incbin >> >> seem to behave as before, which means they only find their target >> files relative to the current directory. Is this intended this way? > Yes. It's currently only the C compiler that has the new code. I see. Do you intend to change the assembler in a way similiar to the compiler in the near future? > No, there is no automatic build triggered by changes. Sometimes I do that > manually. The nightly build checks for any changes since the last build, so > there will only be a new nightly build if something in the source tree has > changed. Okay, I'll try to remember. >> And I'm not clear about the meaning of the last digit (which is typically >> '1'). > > It is a "build number". RPM packages use it to distinguish builds from the > same sources. I'm using it (very rarely) to given the second build on one day > a separate number. Okay. Thanks for the explanation. Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat May 29 20:53:38 2010
This archive was generated by hypermail 2.1.8 : 2010-05-29 20:53:40 CEST