Hello, If you are a developer who wants to port or develop software for AROS ABIv0 (32-bit x86), this post will provide resources to help you with your work. [b]Compiler and SDK[/b] Currently AROS ABIv0 provides GCC 6.5.0. If you plan developing [b]natively (directly on AROS)[/b], the compiler and SDK are already pre-built and available on installation disk. When installing through InstallAROS, select "Install Debugging tools and Developer software" option. After installation, GCC will be available from AROShell and Unix Shell (sh). If you plan developing through cross-compilation, you will need to build cross-compiler and SDK on an instance of Linux. This can be done directly on Linux or indirectly on Windows. If you plan developing[b] through cross-compilation[/b] and you are [b]a Windows user[/b], the recommended method is to build AROS under Linux through WSL. The tutorial on how to do this is available here:[url]https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/[/url]. Please note that tutorial describes setting up environment for 64-bit and 32-bit AROS. In order to build ABIv0 32-bit x86 AROS, please setup up WSL according to first section of tutorial and then scroll down to last section named "If you want to install the i386 version" and follow instructions listed there. Remember to checkout branch alt-abiv0 in both AROS and contrib git clones in this case. Alternatively, you can set up a virtual machine with Linux installed and simply follow the section below. If you plan developing [b]through cross-compilation[/b] and you are [b]a Linux user[/b], you will need to build cross-compiler and AROS directly on your machine. The tutorial for doing this is available here, [url]https://github.com/deadwood2/AROS/blob/alt-abiv0/INSTALL.md[/url]. Be sure to follow section on "Linux-i386". Once you complete these steps, additional steps (building contrib and making cross-compiler scripts) can be followed in "WSL" tutorial: [url]https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/[/url]. Remember to checkout branch alt-abiv0 in the contrib git clone. At this point, whether you are a Windows or a Linux user, you have a cross-compiler available with full SDK as well as local compilation of AROS hosted which will allow you to quickly test your software. [b]Documentation[/b] Your main point of reference should be Autodocs. These are compiled from source code and thus are always up to date. You can find them here: [url]http://www.aros.org/documentation/developers/autodocs/index.php[/url] Next, there are two repositories of documentation on different topics related to AROS. They have different levels of freshness and up-to-dateness, but are good to show general direction. First is developers documentation on www,aros.org, and specifically: [ulist=circle][url]http://www.aros.org/documentation/developers/app-dev/index.php[/url] [url]http://www.aros.org/documentation/developers/zune-dev/zune-application-development.php[/url] [url]http://www.aros.org/documentation/developers/debugging.php[/url] [url]http://www.aros.org/documentation/developers/porting.php[/url][/ulist] Second is developers documentation on AROS Wikibooks, and specifically: [ulist=circle][url]https://en.wikibooks.org/wiki/Aros/Developer/Docs[/url] [url]https://en.wikibooks.org/wiki/Aros/Developer/Porting_software[/url] [url]https://en.wikibooks.org/wiki/Aros/Developer/Zune[/url] [url]https://en.wikibooks.org/wiki/Aros/Developer/Zune/Classes[/url][/ulist] Last group of reference comes from documentation of projects that AROS integrates or re-implements: [ulist=circle][url]https://github.com/amiga-mui/muidev/wiki[/url] [url]https://amigadev.elowar.com/[/url] [/ulist] [b]Contact/Questions[/b] There are multiple ways you can get in touch with other developers to get help and have your questions answered: [ulist=disc]Create a thread in this forum Join #aros channel on AmigaDev discord ([url]https://discord.gg/nU3tH86acb[/url]) PM user deadwood on this forum[/ulist] Also if you don't have any questions, but would just like to share with AROS community what you are working on, this forum is the place to post. Looking forward to hearing from you!

deadwood, in the contrib there are two libraries (freetype2.library and popupmenu.library) which have a different size from the Build, are there any differences, which one should be used?

many thanks deadwood:)

Update 1 is now officially released. For binaries and change log check these locations: [b][url]https://github.com/deadwood2/AROS/releases/tag/ABIv0_20220318-1[/url][/b] [b][url]https://www.axrt.org/downloads-aros[/url][/b]

the alpha iso boot fine i use virtualbox at moment native mode do not work "error intelGMA"

at the moment I don't receive any news from Mr. Alfred Faust about Bars&Pipes I think that anyway there will be further updates Mr. Faust cares a lot about the development of this program, later there will be a new version of WCS also in 64 bit this is a fantastic program and very fun and creative, the Beebase cross-platform relational database will always be updated and there will be a 64 bit version as well, we hope n a midi implementation d Protrekkr professional program to create music, again thanks to Mr. Franck Charlet for the midi implementation on Aros, and as soon as the compiler for the missing plugins will be updated there will be other projects in the works all best!

Thanks Deadwood I'll do some testing but I won't be releasing a new distribution at the moment

Created bug report for this issue: [url]https://github.com/deadwood2/AROS/issues/144[/url]

Well, there is no new ABIv11 release. 20230430-1 is still the "current" one. The previous post was only to inform about updated source in the repository.

deadwood thank you for all you do ! Question, the new Contrib 20230430-1 is only for AROS ABIv11 ? Now I can start creating an Alpha version of AROS One AROS ABIv11.

deadwood, is it possible to correct the graphic artifacts when dragging an Icon ? If you try to drag a native AROS Icon but also a DualPNG Icon, around the Icon you notice black graphic artifacts, see screenshot I specify that on AROS 68k the problem does not exist, especially the DualPNG Icon when dragged and clean and clear !

FYI: The master branch of my AROS repository has been updated with around 220 changes from main AROS repository and is now up-to-date with it. If you have local linux-hosted compilations, it's best to do a full rebuild. The latest builds on build server, for both 64-bit and m68k, contain these changes. Known issues: a) Synchronization of usb 3.0 related work has been delayed to later date. As far as I understand the work is not done and it's possible that is introduces problems with existing 2.0 support b) if you have local pc-x86_64 builds, InstallAROS process is currently broken - it will be fixed before next release. If you detect addition issues after this update, let me know.

I don't find any anomalies

Ok so I can proceed to build the new AROS One 2.5. Regarding the USB image I will probably still use Rufus v3.2 and VHD format, unless in the meantime the new version of Rufus 4.5 will be released (like v4.4 It will only work on Win10/11). Meanwhile, yesterday the developer of Rufus informed me by e-mail that he has finally located the [url=https://github.com/pbatard/rufus/issues/2468][b]Bug[/b][/url] that I had reported to him on the AROS One Images with Rufus v4, referred to by him as "benign error, Read error: [0x0000001B] " and that it will be fixed in the next version.

Thanks. There are no more changes planned for U1 update. Unless some problems are found, the archive above will be the official release.

deadwood, actually I had already tested part of these updates, anyway everything seems to be fine ! In the Build you are going to release will there be more new update ?

Ok, corrected.

@deadwood link don't work ?

I do intend to synchronize patches from Apollo repository, but this is not on priority list right now - at least not for this year. There is a considerable effort in doing this and I want to set aside time to structurally move these changes.

Hello Deadwood, I just looked at Apolloos at github and there was a extensive commit https://github.com/ApolloTeam-dev/ApolloOS/pull/109 it is about screens, something heavily affects software on 68k because on Aros it can happen that a game or app asks for a PAL screen and gets RTG and then crashes. Perhaps it would be possible to update your branch too?