SDK 54.16

As you probably have seen on the site news, the new SDK 54.16 was released. I use that SDK for a long time now, and it is great that it is available for everyone to use. Time for some celebration and a few more beers at the upcoming Amiga events.

I wrote some more info about the changes at https://ko-fi.com/post/AmigaOS-4-SDK-54-16-released-L3L6FHKJY

Please, let me know if you have any issues or questions.

At last :)

thanks! good documentation improvement too and ability to swap between gcc versions.

finally, Reschedule() is available again, making adtools building a lot easier!

@walkero

Nice...

Does it come with third-party stuff, like SDL2 or do I have to insrallv those libs manually?

Thank you to all involved

@Raziel
No added libraries. This is better to be installed by the developers.

@walkero

Thanks a lot, much appreciated!

@walkero

Understood

What is gcc version in this sdk release?

Edit: Just read the changes, gcc from 6 to 11 + vbcc, greaaaat!! Tnx!

There is the new standard library in gcc 11?
If yes, is it complete?

Is it possible a porting of the Object-C module for wayfarer?

@vagappc
Quote:
Are you talking about afxgroup's clib2? If yes, then no, this is not included.

Quote:
As much as I know Objective-C is not supported by our gcc compilers yet. And that part of wayfarer is not open source.

Excuse me, my ignorance.
But with the new SDK, is possible porting of the last version of Odissey?

What do you mean by porting the last version of Odyssey?
Do you mean to compile natively on an OS4 system? This will be quite slow and possibly fail because of cmake. Odyssey is able to be compiled using a cross-compiling dev environment with any SDK version.
The new SDK 54.16 doesn't bring a newer version of cmake.

Now the last version of Odissey is the 1.23 rc5.
But on MorphOS and AROS exists the 1.25.

@vagappc
Have you seen the source of these releases somewhere? If yes, then I guess it could be merged by someone who would like to do it in OS4 Odyssey repo and build it.

@vagappc
Quote:

Latest version of Odyssey on MorphOS is 1.24 by original author - Fab. Then, on top of that aros developer DeadWood made an 1.25 version (which have more updated webkit core and some other stuff). I do have 1.25 binary builds for os4, but it not functional (just shown a non functional window, need fixes and debugging to make it works).

Any of those versions didn't need anything which can't be compiled with old compilers like 4x or 6.x, so problem is not updated GCC. More of it, some of us already use very latest GCC (11.3.0) self-compiled from Adtools (the same as happens inside of SDK, in this regards nothing new there). Problem is that just no one except me wish to build 1.25 version, which already too old (the same as our version of Odyssey).

About Wayfarer from morphos : ObjectC there used only for build gui and stuff on top of WebKit, which was and still C/C++ based one. What mean that we don't need ObjectC to have a working webkit core. ObjectC is just personal wish and choose of morphos developers. We don't need ObjectC support to have make a browser on top of WebKit, anything else can be used for GUI, even pure simple C, just we need to port a WebKit to some "class" (like html.mcc was for MUI in early days) or to shared library instead, and then build stuff on top of it.

To summorize : new SDK didn't bring anything radical which we didn't have before, especially in terms of webkit core or 1.25's aros port.


@walkero

Quote:

Once you will start building webkit yourself, you will see that merged and build non possible, as they (webkit devs) change the layout and structure of their code so fast and so radically, that you end up with almost fully new code, without merging and build possible, but instead you leaves with porting new version from scratch, and add all the changes from old one, to new one with some modifications

@kas1e
[quote]Once you will start building webkit yourself, you will see that merged and build non possible, ...[/code]

I didn't mean that it would be something like a simple merge and everything would be great and brand new. I meant that it will need to get that 1.25 code and merge it, doing all the necessary changes to make it work for AmigaOS 4. Sure it needs hard work to make it usable.

@walkero

Are we the only community still actively using BE on their platform of choice?

While I know that mainstream platforms are all based on LE there ought to be at least one (portable) "modern" and still developed BE browser alternative...or isn't there?

@Raziel

Well no, the M68K (Atari, AmigaOS) community is BE.

I guess NASA, the US military, and other governments slow to adapt new untested technology. I know PowerPC was used in printers, its used in Network Routers.

ARM is almost impossible this days, Covid lockdowns in China and other issues, maybe PPC can come back.

I think we need to beg AMD to make killer PowerPC chip with the latest technology.

@walkero

There's a bug in the install script where it overwrites the last line of user-startup.

This was my user-startup (last two lines)
Quote:
and this is user-startup after the installation was finished
Quote:

@Raziel
Thank you for this comment. I noted it to be fixed in the next SDK release, if possible.