Thanks to the team we now have an updated SDK
Does it follow the same advice as the pre 6 OS updates to install it into a fresh dir/partition and let AmiUpdate do the rest?
Or has it the ability to be upgraded over an old SDK (with all AmiUpdates)?
I'd fancy the second but think it's safer to do a new full install plus updates...
SDK 53.24 ... and followups
SDK 53.24 ... and followups
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
- tonyw
- AmigaOS Core Developer
- Posts: 1479
- Joined: Wed Mar 09, 2011 1:36 pm
- Location: Sydney, Australia
Re: SDK 53.24 ... and followups
A few betatesters installed it over existing SDK installations without problems, but it's always safer to make a clean installation.
cheers
tony
tony
- salass00
- AmigaOS Core Developer
- Posts: 530
- Joined: Sat Jun 18, 2011 3:12 pm
- Location: Finland
- Contact:
Re: SDK 53.24 ... and followups
The installation instructions still recommend doing a fresh installation so that's what I did here.
Re: SDK 53.24 ... and followups
Great to see an updated SDK.
Is there a way to see which functions are new or updated ?
A "What's new" file, maybe ?
Thank you OS4 team !
Is there a way to see which functions are new or updated ?
A "What's new" file, maybe ?
Thank you OS4 team !
http://apps.amistore.net/zTools
X1000 - AmigaOS 4.1.6 / 4.1 FE
X1000 - AmigaOS 4.1.6 / 4.1 FE
Re: SDK 53.24 ... and followups
I did a fresh install, just copied over third party soft like subversion.
Mick did such a great job in managing the SDK updates that it has been a cake to install and update
Thanks a lot to all
Mick did such a great job in managing the SDK updates that it has been a cake to install and update
Thanks a lot to all
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Re: SDK 53.24 ... and followups
I think it would easier if you just did a diff -r between the old one and the new one.zzd10h wrote:Is there a way to see which functions are new or updated ?
A "What's new" file, maybe ?
I didn't want to spend time explaining all the details in a text file nobody will ready anyway.
ExecSG Team Lead
Re: SDK 53.24 ... and followups
While recompiling my source, at least one change found: there is no IDOS->GetProgramName() anymore, but probably the new IDOS->GetCliProgramName() is renamed version. And there seems to be a change of application.library interface version needed according to autodoc.ssolie wrote: I didn't want to spend time explaining all the details in a text file nobody will ready anyway.
Yes, I understand that doing a ChangeLog takes some time, but it also helps to adapt the sources to a new SDK.
Marko
Marko
Re: SDK 53.24 ... and followups
Yes, if you're using interface v1 (which you will be), OS4 complains profusely when launching your application. It has to be interface v2 when using the new includes. This almost certainly means nothing newly compiled using application.library will work on OS4.0.blmara wrote:While recompiling my source, at least one change found: there is no IDOS->GetProgramName() anymore, but probably the new IDOS->GetCliProgramName() is renamed version. And there seems to be a change of application.library interface version needed according to autodoc.
There's a new tag to create an alpha channel out of 8-bit picture DT subclasses, some new tags for SetWindowPointer to get the new pointer shapes, some new commodities.library functions to get a list of running commodities and send them messages, dos.library has some new functions and a new function table interface for filesystems and... that's all I've discovered for now.
Usually I miss some new functionality, so a changelog would be useful.Yes, I understand that doing a ChangeLog takes some time, but it also helps to adapt the sources to a new SDK.
Re: SDK 53.24 ... and followups
Both of these changes should be covered by the SDK FAQ now.blmara wrote:While recompiling my source, at least one change found: there is no IDOS->GetProgramName() anymore, but probably the new IDOS->GetCliProgramName() is renamed version. And there seems to be a change of application.library interface version needed according to autodoc.
ExecSG Team Lead
-
- Posts: 314
- Joined: Mon May 14, 2012 10:26 pm
- Location: 日本千葉県松戸市 / Matsudo City, Chiba, Japan
- Contact:
Re: SDK 53.24 ... and followups
Well I ran into a weird problem...
The SDK Installer decided to cut off everything past the entry for the SDK in my User-Startup sequence
and as that entry was near the beginning... obliterated ALL of the file following...so I lost the MUI and Application assigns for everything else installed.
Neat fun... not... is the Installer suppossed to have exclusive control or have any trigger for "cutting short" files like that ?
repeat installation did not repeat this fault... so something about my original User-Startup triggered the misbehaviour
The SDK Installer decided to cut off everything past the entry for the SDK in my User-Startup sequence
and as that entry was near the beginning... obliterated ALL of the file following...so I lost the MUI and Application assigns for everything else installed.
Neat fun... not... is the Installer suppossed to have exclusive control or have any trigger for "cutting short" files like that ?
repeat installation did not repeat this fault... so something about my original User-Startup triggered the misbehaviour
Last edited by Belxjander on Sun Oct 13, 2013 6:57 am, edited 1 time in total.