Hi,
I've just created a vagrant environment to use for AmigaOS4 cross compiling development. You can use it on any OS that has Vagrant (Linux, Windows and MacOS).

What is it?
* Virtual Linux environment with pre-installed AmigaOS 4 PowerPC compiler (gcc 5.5.0) and latest official SDK.
* Scripts to download SDK dependencies from third party source (f.i. os4depot) with distributed instructions.

Read more on how to install here: https://sourceforge.net/p/vagrant-amigaos4-crosscompiler/wiki/Home/

Testing, questions and suggestions are welcome!

_________________

@jaokim

Maybe provide "build for OS4 as a service" in the cloud in a not too distant future? :)

Should be quite possible, using gitlab-ci, or jenkins, and docker image with above setup.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@jaokim

I hope this make easier to compile and work on alien Linux things.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Given that the GCC version is later than the one in the SDK, it might be easier to port Linux stuff. The main aim is however to simplify the process of setting up the environment and dependencies. The dependency installer script should be possible to run on AmigaOS as well.

@kolla:
Now that would be interesting! I guess this could work as a starting point for such a thing.

_________________

@jaokim

Nice one. Thanks. At first I thought the thread was called "Virtual Linux box for AmigaOS4 in development" and it was going to be a dedicated Linux installer that could run OS4.

Last edited by Hypex on 12-Aug-2018 at 05:48 PM.

@kolla

Quote:

Maybe provide "build for OS4 as a service" in the cloud in a not too distant future? :) Should be quite possible, using gitlab-ci, or jenkins, and docker image with above setup.

How would that work practical? Would you need to check in your code to svn, and let the remote server download and build it, or could something like distcc be used?
The ideal would be to have something on your local Amiga that overrides a normal make, and handles the remote copying and compiling, so that it works transparently. But that might be overkill? Perhaps just a script that handles most of the stuff...

Then there’s the question of how users are separated. Perhaps some ticket system... Hmm...

_________________

@jaokim

Thanks!

But I think I'm missing apiece:

arexxxml-code$ sudo install-sdk-dependency.py
[sudo] password for billt:
sudo: install-sdk-dependency.py: command not found

arexxxml-code$ ls
ARexxXml.cpp ARexxXmlException.h dependencies.json Makefile XmlHandler.cpp
ARexxXmlException.cpp ARexxXml.h main.cpp test XmlHandler.h



And I can't run vagrant: (TEMPLATE_vagrant-amigaos4 here is my equivalent of your example's proj6)

TEMPLATE_vagrant-amigaos4$ vagrant up
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.




This is under Kubuntu 17.10 in a VirtualBox VM on top of my Win10 laptop.

Last edited by billt on 13-Aug-2018 at 06:14 PM.

_________________
All glory to the Hypnotoad!

@billt

Did you try to run vargrant on the linux side, or the Windows side?

Since you have VirtualBox on your Windows machine, you should download Vagrant for Windows, and try it from there. I.e. do “vagrant up” from the windows command line. I’ve never run it in Windows though, so not 100% sure on how it’s done exactly.

It might also be possible to try and find VirtualBox for your Kubuntu (something like “apt-get install VirtualBox”), but I don’t know if that’s too many VirtualBox in top of each other.

_________________

@jaokim

Quote:

How would that work practical? Would you need to check in your code to svn, and let the remote server download and build it, or could something like distcc be used?

Hm, svn? Don't know about that, I have moved to git :)

No, first you provide a docker with the needed content to do cross-buidling.
Then you upload it to a repository available from for example gitlab.com.

Now users can create a git repo with their Amiga source code, and a .gitlab-ci.yml file that describes what docker image to use (the above), how to copy the Amiga source code into the docker, how to do the build, and how to dump the result (ideally a logfile and an lha, for example) to somewhere the user can download it.

An important thing to understand with docker, is that once it is done with its work, it is supposed to exit and vanish from existence. Next build will download from repository (except that it will use a cache if checksum are the same) and build in a clean environment.

Using the built in hooks of gitlab, all the user needs to do is push a commit of the code, and gitlab-ci will fire up the docker, build the source code, and dump out lha+logfile, which user can download.

How to do this from Amiga? Well, I currently use rsync from Amiga to a directory on a local linux host (strictly speaking, it is a raspberry pi zero mounted inside the Amiga), and then send off some rsh commands to do the git part, so that it all ends up in a git repo over at gitlab.

Last edited by kolla on 13-Aug-2018 at 09:24 PM.
Last edited by kolla on 13-Aug-2018 at 09:23 PM.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@jaokim

I ran in Linux. It never occurred to me that vagrant is a MSWindows command...

I've never used vagrant before, and perhaps I don't understand what it is, and what you assume I already know before starting your quickstart instructions.

Am I supposed to provide a VM for vagrant to run on, or run beside, or under?

I had taken your quick start instructions as to make sure vagrant is installed on my Linux, then get your repository, and run up and ssh from there, and off it goes... It seems now that is not the case.

And the missing file in the arexx part? Should that be part of retrieving that other repository as well, or is it separate somewhere?

_________________
All glory to the Hypnotoad!

@billt

You have to download Vagrant for Windows first. Follow the link in the first step. Then you should be able to follow the next steps.
1. Install Vagrant
2. Download the vagrantfile from the svn-location
3. Do “vagrant up” from Windows, which will download a Linux image, start it in vagrant (or really VirtualBox) download SDK and stuff.
4. “vagrant ssh” from Windows, will start an SSH session into the VirtualBox Linux, where you should be able to download the arexxxml example and download decencies.

Hopefully it’ll work.
My instructions were perhaps a bit too “quick” :)

_________________