[cc65] Chicken and Egg Problem (?)

Hi,

Frameworks (in contrast to libraries) tend to come with a generic
main() calling into the application-specific coding. In this scenario
the main() typically lives inside a library. Contiki is a example for
such a framework.

Up to now things worked nicely because the startup code was always
pulled in. And from there callmain was referred from the C/runtime
library. Leveraging the --start-group / --end-group options the
C/runtime library would then successfully pull in main() from the
framework library.

But now with the startup code living in the C/runtime library the
whole thing doesn't get started if main() lives in a library - at
least that's how things look to me.

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