@afxgroup
Quote:
I'm plan also to create a clib2.library but this will come later
Building a new version of clib2.library should be no problem at all, the first one I build was about 20 years ago already, and there were no big problems at all converting it to a shared library.
Except for the C library functions using global data of course, I used a small static link library for such functions instead of including them into the shared clib2.library, but with the current (maybe beta only) kernels you should be able to use thread local storage in clib2.library instead.
Just make sure you update all relevant data types to 64 bit (files, time, date, etc.) before releasing the first version of your clib2.library, or you'll get into the same problems as I did with newlib and you'll have to create an incompatible V2 (64 bit data types) interface way too soon as well.
Edited by joerg on 2022/3/13 4:58:26
Edited by joerg on 2022/3/13 5:52:34