[cc65] Secondary Linker Config for C64 Overlays (was: Specifying segment for library code?)

Hi,

>> Why that? Anything I should know but don't remember?

> Because you added the "%o.ovl" feature to the linker I asked you for
> and I commited to create generic overlay linker configs for the CBMs,
> Apple and Atatri using it instead of the "fixed" example. But I didn't
> do so by now :-(

Okay, I just added a secondary linker config for overlays on the C64
called 'c64-overlay.cfg' following the "single linker session"
approach. Additionally I added an 'overlaydemo.c' sample program
showing how to use it.

Remarks:
- Docs are missing so far
- Other targets are missing (at least the Apple2 will follow pretty soon)

As the linker config can't "know" how many overlays are desired it
just assumes 9 overlays and produces files "%O.1" ... "%O.9". The
corresponding segments are optional but all nine output files are
always generated. I personally would like to see ld65 to create only
non-empty files.

However I presume that there are specific reasons for ld65
creating/keeping empty files. In that case maybe an 'optional'
attribute for memory areas would make sense...

Regards,
Oliver
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.