Development Plan

[Amiwell]

ok deadwood

[AMIGASYSTEM]

Hello,

Some good news from me. I've been working over last 3 weeks to fully define ABIv11 call conventions which is now done. This also means there is first official release of ABIv11 for x86_64!

First, link to ABI documentation: https://github.com/deadw00d/AROS/blob/master/arch/x86_64-all/ABI_SPECIFICATION

Next, link to releases (bottom of page): https://axrt.org/index.php?tab=download-aros

I also prepared first "3rd party" application - a build of MPlayer is now available on Archives: http://archives.aros-exec.org/index.php?function=showfile&file=video/play/mplayer-1.0-v5.x86_64-v11-aros.zip

The change to calling conventions means that if you already created and published an application for ABIv11 they will no longer work. Please get in contact with me and we will figure out a solution. If you have local builds of ABIv11, please rebuild them (including cross-compilers) from scratch after 'git pull'.

The last month's C library re-design and this change are the last major impacting changes that I had planned for ABIv11. This nicely closes off 2021 and opens 2022 for incremental improvements and growth.

If you want to try compiling some applications, downlod the "System" archive, the "Contrib" archive and copy the files from "Contrib" into "System". This will install GCC 6.5.0 for you. Contrib archive also contains 'make' and other basic unix utilities which should help you with compilation. Be sure to run AROS with at least 256MB RAM (-m 256). When uploading to AROS-Archives, please use the "x86_64-v11-aros" suffix of archive file names (see MPlayer example).

This change will also affect ABIv0  ?

[magorium]

This change will also affect ABIv0  ?

No, these changes will not affect ABIv0.

Actually you quoted the answer yourself already 

This also means there is first official release of ABIv11 for x86_64!

e.g. it is named ABIv11 for a reason 

[Amiwell]

If you want to try compiling some applications, downlod the "System" archive, the "Contrib" archive and copy the files from "Contrib" into "System". This will install GCC 6.5.0 for you. Contrib archive also contains 'make' and other basic unix utilities which should help you with compilation. Be sure to run AROS with at least 256MB RAM (-m 256). When uploading to AROS-Archives, please use the "x86_64-v11-aros" suffix of archive file names (see MPlayer example).

ok understand I tried to compile something but I always receive mistakes, I stop here

[miker1264]

If you want to try compiling some applications, downlod the "System" archive, the "Contrib" archive and copy the files from "Contrib" into "System". This will install GCC 6.5.0 for you. Contrib archive also contains 'make' and other basic unix utilities which should help you with compilation. Be sure to run AROS with at least 256MB RAM (-m 256). When uploading to AROS-Archives, please use the "x86_64-v11-aros" suffix of archive file names (see MPlayer example).

ok understand I tried to compile something but I always receive mistakes, I stop here

Fixing the errors is the most fun. 

[deadwood]

This change will also affect ABIv0  ?

No, these changes will not affect ABIv0.

Correct

[AMIGASYSTEM]

Thanks deadwood, specifically I was referring to the fact the new feautures will be ported to ABIv0 as well.

[deadwood]

Thanks deadwood, specifically I was referring to the fact the new feautures will be ported to ABIv0 as well.

Ok, now I understand. The calling convention will not - it is specific to x86_64. The reworked C libraries will become available in ABIv0 at some point.

[deadwood]

Hi,

As indicated earlier, I made plans for next milestones - you can find them below. They are listed in an order I plan working on them.

1) Release new version of AxRuntime based on recently releases ABIv11
2) Migrate ABIv0 from GCC 4.2.4 to GCC 6.3.0. This will provide better tooling for 3rd party developers.
3) Release new version of ABIv0 refreshed to common codebase from around 2019-03-01 (Today we are on 2018-04-15)

[OlafS3]

Hello Deadwood

question again (sorry do not want to nerve)

have you looked at the "software not correctly closes"? That was what I reported that f.e. demos but also applications not correctly close and you only get a empty screen and you have to reboot

[Amiwell]

Hi,

As indicated earlier, I made plans for next milestones - you can find them below. They are listed in an order I plan working on them.

1) Release new version of AxRuntime based on recently releases ABIv11
2) Migrate ABIv0 from GCC 4.2.4 to GCC 6.3.0. This will provide better tooling for 3rd party developers.
3) Release new version of ABIv0 refreshed to common codebase from around 2019-03-01 (Today we are on 2018-04-15)

Thank you deadwood

[deadwood]

Hello Deadwood

question again (sorry do not want to nerve)

have you looked at the "software not correctly closes"? That was what I reported that f.e. demos but also applications not correctly close and you only get a empty screen and you have to reboot

It's on my list, but I haven't looked into it yet. Its probably more effective if you try interesting someone from Apollo team in this issue as well - they are more engaged with m68k than I am.

[magorium]

@deadw00d
It is of futile importance but on your axrt downloadpage it is spelled desription (but should read description)

... and while i'm at it 

@salvo:
In your sig: It is spelled Maintainer and not Manteiner

[Amiwell]

ok magorium

[miker1264]

@deadw00d
It is of futile importance but on your axrt downloadpage it is spelled desription (but should read description)

... and while i'm at it 

@salvo:
In your sig: It is spelled Maintainer and not Manteiner

Just minor infringements. Probably due to faulty keyboard layout. 

salvo though is a different matter. He just can't spell right.