Tony Pavlov

yes, this bug is pretty annoying :(

any news on this, Philipp?

it does not, it is ok to close this issue.

because the order of linking matter. the order how you pass the object files into the linker through the command line or the link file. on almost every system, including modern, order of linking matter.

because the order of linking matter. on almost every system, including modern, order of linking matter.

the gbdk-2020 design is quite convenient, and proven flexibility and extensibility, when porting to the number of platforms (consoles and computers) _CODE is for the user code and the library code. _HOME is for the non-switchable code (trampolines, C support functions, ISR's, user non-switchable code), entry point and interrupt vectors, if applicable, is in the fixed _HEADER section (marked with absolute attribute). such design make sense, at least for the most of the 8-bit platforms.

the gbdk-2020 design is quite convenient, and proven flexibility and extensibility, when porting to the number of platforms (consoles and computers) _CODE is for the user code and the library code. _HOME is for the non-switchable code (trampolines, C support functions, ISR's, user non-switchable code), entry point and interrupt vectors, if applicable, is in the fixed section (marked with absolute attribute). such design make sense, at least for the most of the 8-bit platforms.

the gbdk-2020 design is quite convenient, and proven flexibility and extensibility, when porting to the number of platforms (consoles and computers) _CODE is for the user code and the library code. _HOME is for the non-switchable code (trampolines, C support functions, ISR's), entry point and interrupt vectors, if applicable, is in the fixed section (marked with absolute attribute). such design make sense, at least for the most of the 8-bit platforms.