AxRuntime

[deadwood]

I assume you refer to Arix? As far as I know Michal wanted to take it one step further that I do - create a new, better API. I think both project have similar trajectory and they could definitely share code between each other. I think Michal has his hands full with emu68 at the moment though.

[OlafS3]

I assume you refer to Arix? As far as I know Michal wanted to take it one step further that I do - create a new, better API. I think both project have similar trajectory and they could definitely share code between each other. I think Michal has his hands full with emu68 at the moment though.

And what is your vision? Creating a "aros layer" like the win32 api on 64bit windows?

Yes Michal sounds like he wants to go further. But perhaps there is some room to work together. And yes I think too he is busy with emu68 at the moment (and propably for some time)

[deadwood]

There are two goals I want to eventually reach. First is to turn a standard Ubuntu/Linux Mint desktop into something that feels like an Amiga-like system so that on a surface you don't see a difference between this and native AROS. Second is to extend lifetime of still-developed Amiga applications by giving authors a much much bigger user base (= Linux community).

[OlafS3]

There are two goals I want to eventually reach. First is to turn a standard Ubuntu/Linux Mint desktop into something that feels like an Amiga-like system so that on a surface you don't see a difference between this and native AROS. Second is to extend lifetime of still-developed Amiga applications by giving authors a much much bigger user base (= Linux community).

sounds like a concept 

perhaps the maintainer of icaros desktop is interested to make something. That would be something people always asked for

[deadwood]

Hi

I'm sharing with you results of my latest developments! So far it was possible to build an Amiga application as a Linux executable with AxRuntime. I already recompiled MPLayer and WookieChat so time ago and I'm actively using AROS MPlayer under Linux Mint as my media application. What was so far not possible however is to run an executable from within AxRuntime program itself. Think Shell - it is a command line program that allows you to run other programs, write scripts that run other programs, pipe output of one program to another and so on. Now, with the latest developments I've made a step towards enabling this where a program that is compiled to work with AxRuntime can be started from Linux but at the same time can be started from AROS Shell. Here is a nice screenshot:



We are not yet fully there, more work is needed but it is functional enough to provide first preview builds. Since this is work in progress build, there is no new AxRuntime release yet. The archive below packages together AROS-Shell with runtime so that it is fully independent and can be started without installing additional dependencies. You can download AROS-Shell from here: https://axrt.org/development/AROS-Shell-20220221.zip

I'm open to feedback and I'm always available to help out if you want to try to compile your Amiga application to run natively on Linux using AxRuntime.

[cdimauro]

Impressive. One question: are "Ax applications" able to communicate each other, like on Amiga o.s.? Or is each application fully isolated?

[OlafS3]

@deadwood

really impressive

[deadwood]

Impressive. One question: are "Ax applications" able to communicate each other, like on Amiga o.s.? Or is each application fully isolated?

That's a complex question to answer - depends on what do you mean by "communicate". Each Ax application is an separate Linux process so by default they have separate address spaces.. however if an Ax application is started from another Ax application (RunCommand, System) they then share address spaces. I think in future it will even be possible to have communication between two Ax applications started from Linux - it all depends on needs of developers. If there are valid use cases for this I will look into providing such functionality.

[OlafS3]

one question... is it possible to combine Linux components with aros? I mean f.e. using a Zune GUI that access linux components using linux API?

[deadwood]

Yes, you can You can create applications that have Zune API and use all other Linux libraries. For example, Ax-compiled MPlayer uses Zune GUI but the C library is the Linux C library, not the AROS one.

[OlafS3]

Mr. Spock would say "fascinating" 

[OlafS3]

I think to create interest in the community you must have something to show. I mean f.e. having wanderer desktop running on it and you launch linux applications that would create a lot of interest in it. I saw video running wanderer on top of linux already. It would be nice (naive said) if it would also include linux apps so you could launch firefox from it as if it would be a aros app. And of course wanderer in full screen mode as a full desktop.

[deadwood]

I follow your reasoning and I will definitely help and suggestion with regards how to interest people in using it once I have ground work done. I'm still experimenting with certain aspects.

[OlafS3]

I follow your reasoning and I will definitely help and suggestion with regards how to interest people in using it once I have ground work done. I'm still experimenting with certain aspects.

yes just ideas...

I think if ground work is done and wanderer works like a linux desktop integrating both aros and linux apps there will be real interest at it

[cdimauro]

Impressive. One question: are "Ax applications" able to communicate each other, like on Amiga o.s.? Or is each application fully isolated?

That's a complex question to answer - depends on what do you mean by "communicate". Each Ax application is an separate Linux process so by default they have separate address spaces.. however if an Ax application is started from another Ax application (RunCommand, System) they then share address spaces. I think in future it will even be possible to have communication between two Ax applications started from Linux - it all depends on needs of developers. If there are valid use cases for this I will look into providing such functionality.

The current implementation is certainly better, because it offers part of processes isolation which was completely missing on Amiga o.s. & co..


Communicating between two application was usually common on the Amiga o.s. land. AREXX was the most notable example of applications that communicate each other via message passing, using the AREXX runtime which was a facilitator, and of course this requires sharing the same address space.


However, and as I stated at the beginning, the current implementation of the AxRuntime is more solid and definitely preferable. The option to share the address space is second priority.