New verson of CLiB2 from Andrea (afxgroup)

@Corto
I am sure Andrea will answer better as it he who do all the work, but from my POV reassons are:

1). get rid of all os3 code, as it only make things be worse for us
2). implement all the missing posix stuff to make easy porting
3). implement all the other stuff like wchars, shared objects and all what we may have or may not have with newlib
4). as it opensource, we will have no issues as with newlib waiting years for releases.

And so on.

At some point it should replace clib2 in our SDK if everything will be well, and if there will be wish from SDK mantainers. But in meantime it can be the same independent C library, which you can replace in your SDK yourself if you want. I already use Afxgroup's version to build few projects, so its matured enough. At least things like SDL2, few games, and co works well with already.

@afxgroup

I installed your beta and let ScummVM configure run with it.
Unfortunately i was stopped early


Something missing?
Or did i forget to add some stuff?

The only thing i changed (compared to newlib) was to add to CXXFLAGS, so it gets picked up instead of newlib.

Help?

Thank you

g++: error: unrecognized command-line option '-Wpragma-pack'

It seems a problem on gcc not on clib2

However regard clib2. The purpose is to have a C library that doesn't require ages to be updated like newlib. If we find bugs or we want to implement some new stuff we can do it. And read well "WE". I mean. We are in 2022 not in 1990 where closed source was the rule. Today the open source is the solution but no one in Amiga Land understand this (Even Microsoft has learn the lesson).
I hope that all of you will help the project. I'm pretty sure there are bugs because i've made really a lot of changes.
So this is the purpose. I cannot rely anymore on newlib for my projects because Hyperion/Aeon/God/Satana are not reliable. Not anymore.

I've published a new beta

https://github.com/afxgroup/clib2/releases/tag/v1.0.0-beta-2

Use this one that has a lot of improvements and fixes

@afxgroup

Nice, thank you

@afxgroup

Question...does the clib2 dir go into SDK: (root) or to SDK:local/clib2?

SDK:clib2

In local folder are installed are third party libraries

@afxgroup

ty

@All
Just want to point out that new clib2 is pretty advanced already in compare with old one: i already have working builds for clib2 of those "big" libs : Irrliht Engine, SDL1/SDL2 and GL4ES. Also have build some heavy os3/68k game over new clib2 as well.

So step by step it start to be pretty good in compare with newlib with only differene that is not shared amiga library at the moment. But from other side it's open for everyone, so everyone can fix/update things in.

It also do support all that wchars/wctype/etc stuff, out of box, as well as have dummies for ipv6 defines/structs (yes, while they not works of course because of roadshow, you have no needs to worry about as all compiles out of box).

It also looks like that in end, many 3d party libs on os4depot do have clib2 versions of libs, but not all the time. For example old SDL_Mixer/Mikmod/Modplug for SDL1 miss the clib2 versions, or libbz2, or flac. But all of them of course can be recompiled too.

@Raziel

Quote:

As afxgroup mentioned, it is better to have it in SDK:clib2. In local folder you usually install libs and include files that are comming from third party packages, and they are not deleted/overwritten in case you do an update of the SDK in the same folder. But the SDK:clib2 will be deleted with an SDK update, and will be replaced with the SDK version.

@afxgroup
Great work. I will test it today with my projects, but I am sure that Kas1e's projects are much better to test things like that. And I am glad that they work so good.

Quote:
That would be good to have, but not a show stopper, in my opinion.

HI, recompiled openurl (ReAction) and listed dependencies and noted that with "original" CLIB these 2 resources/libs aren't "added":

elf.library
sysvpic.library

using clib2 (beta2) it adds these 2 resources/libs.

Just courosity.

@Javier
Dunno about elf.library, but sysvpic.library is added for sysv functions. Without sysvpic.library new clib2 will of course still work, just when one will try to use sysv functions clib2 will return ENOSYS, but when library in place they will work as expected.