What I mean by "compatibility" is that when I get an app from (https://arosarchives.os4depot.net/), more than half the time simply trying to run it in ABIv1 will make it crash. So my thinking is that it probably needs to be compiled specifically to run on that version. That's where my idea stems from.
I'm thinking a bit like the Gentoo packages, only different.
@AMIGASYSTEM - Actually, my concept isn't correct, but usually the word “compatibility” is the term that everyone understands, even those who are less experienced. Perhaps talking about libraries might not be understood as it should be.
We should be factual and consistent otherwise it leads to confusion.
Actually, my concept isn't correct, but usually the word “compatibility” is the term that everyone understands, even those who are less experienced. Perhaps talking about libraries might not be understood as it should be.
Furthermore, ABIv0 used by the new distributions is not even compatible with the old ABIv0 builds; the recent ABV0s are compiled with the C library.
Using generic term like "compatible" in this context can be confusing. Let's be more specific, for the sake of new people coming to AROS and reading this:
1) Software compiled with old C library still works on current builds, because that library is still present
2) Software compiled with new C library will not by default start on pre-new-C-library builds, because they don't have the new C library.
Now, would it be possible to create a small app that is compatible with both v0 and v1?
I'm not sure how familiar are you with Amiga concepts. There is something on the Amiga called Installer which allows users to write simple installation scripts. I actually saw a few of those scripts being made cross-system, that is one script that detected what system it is running on (AmigaOS, MorphOS, AROS, etc) and the installs the pre-compiled binary correct for that system. I think it should be possible to call shell commands from that installer script.
Edited by deadwood on 23-12-2025 03:38, 4 months ago
@Amiwell79 - The lead developer works on the abiv0 32-bit branch and the abiv11 64-bit branch. This is to ensure that builds are always up to date and functional on both branches. Backports are made from abiv1. Here on the forum, you can see what has been done recently in the development section.
There is no lead developer… if anyone would be considered the lead developer it would be kalamatee and he doesn’t even consider himself that… so please refrain from spreading false information.
Edited by terminills on 23-12-2025 00:56, 4 months ago
The lead developer works on the abiv0 32-bit branch and the abiv11 64-bit branch. This is to ensure that builds are always up to date and functional on both branches. Backports are made from abiv1. Here on the forum, you can see what has been done recently in the development section.
Hi!
I've been tinkering with Aros for a few days now and I've had an idea which might be useful in making things a lot easier for the user.
I did notice that programs that work with ABIv0 will not always work on ABIv1 and vice versa. The only way to make them work is often through a recompile.
Now, I've found that not all variants work nice with all machines. For example, my netbook seems to like ABIv1 but not the programs. While ABIv0 works so-so but more programs work. And to me that is the core of the problem.
Most apps are just zipped or LHA'd files that are pre-compiled for either one.
Now, when the source code is available, it is possible to re-compile an app; but that can be a bit of a pain for the regular user.
Now, would it be possible to create a small app that is compatible with both v0 and v1?
If so, why not make a new file format that would be just a renamed zip that contains the source files. You double click on it and the compiler/installer app copies the file's content to the ramdisk, proceeds to do the compilation and gives you back a program that stands more chances of working on the chosen variant. Maybe even offer to copy the files to the correct paths and give out a log file telling where the files went for future removal.
That would be a lot cleaner than asking the user to open the terminal and compile it himself while providing the same level of functionality.
What do you think?
That's an interesting idea and could be possible with smaller apps. It might not be feasible with larger apps though. In the meantime anything you want ported to abiv1 just lets me know and I will see what I can do.
Edited by amigamia on 23-12-2025 08:05, 4 months ago
First of all, ABIv0 and ABIv1 are totally incompatible with each other!!!
Many AROS applications include sources in the archive, but almost all of them were compiled for ABIv0 and many of them have now been compiled for ABIv11 64bit.
Furthermore, ABIv0 used by the new distributions is not even compatible with the old ABIv0 builds; the recent ABV0s are compiled with the C library.
As I mentioned, there is not much software available for ABIv1.
My advice is not to reinvent the wheel, to avoid many problems. With your AROS One z5 (which I also own), if you install AROS One ABIv0 ‘32-bit’, you will have all the compatible hardware, including Wi-Fi. Furthermore, to open LHA, ZIP, RAR, TGZ, GZ and many other archives, just double-click on the file, you can also do the same thing on with Dopus4.
In addition to archives, audio, video, image and other types of files are also recognised by Workbench and Dopus4.
AROS One includes “all” the best software available for AROS, and you won't need to recompile anything.
Hi!
I've been tinkering with Aros for a few days now and I've had an idea which might be useful in making things a lot easier for the user.
I did notice that programs that work with ABIv0 will not always work on ABIv1 and vice versa. The only way to make them work is often through a recompile.
Now, I've found that not all variants work nice with all machines. For example, my netbook seems to like ABIv1 but not the programs. While ABIv0 works so-so but more programs work. And to me that is the core of the problem.
Most apps are just zipped or LHA'd files that are pre-compiled for either one.
Now, when the source code is available, it is possible to re-compile an app; but that can be a bit of a pain for the regular user.
Now, would it be possible to create a small app that is compatible with both v0 and v1?
If so, why not make a new file format that would be just a renamed zip that contains the source files. You double click on it and the compiler/installer app copies the file's content to the ramdisk, proceeds to do the compilation and gives you back a program that stands more chances of working on the chosen variant. Maybe even offer to copy the files to the correct paths and give out a log file telling where the files went for future removal.
That would be a lot cleaner than asking the user to open the terminal and compile it himself while providing the same level of functionality.
What do you think?
You can view all discussion threads in this forum. You cannot start a new discussion thread in this forum. You cannot reply in this discussion thread. You cannot start on a poll in this forum. You cannot upload attachments in this forum. You cannot download attachments in this forum.
AMIGASYSTEMDistro Maintainer