In the first and second parts of this series, we saw how to set up a CI/CD solution for Amiberry, using self-hosted runners. The workflow will automatically build on every new commit, but also create and publish a new release (including binaries and an auto-generated changelog), based on the git tag. So generally it works… Read More: CI/CD for Amiberry using Github Actions (pt 3) »
In the previous part of this series, we saw how to set up some self-hosted runners on my local devices, connect them to a Github repository and prepare to give them some jobs. I want to use this setup to automate builds of Amiberry whenever I push a new commit, as well as publish new… Read More: CI/CD for Amiberry using Github Actions (pt 2) »
The Amiberry emulator supports multiple platforms, so if you want to provide binaries on new releases (like I do), you’ll have a lot of compiling to do. Now, you could just compile a binary manually for each platform you have available, but that would take (very) a long time (especially if you have some slow… Read More: CI/CD for Amiberry using Github Actions (pt 1) »
It’s time to see how exactly we can use our shiny new render farm, that we’ve spent the last parts setting up. So without further delay, let’s jump right into it. First things first We will need something to render: A simple scene is enough, as long as it has multiple frames (remember, each render… Read More: (Amiberry powered) Lightwave render farm, (pt 5) »
Next we need to install Amiberry itself. If you’re using the recommended Raspberry Pi OS, then you can use the pre-compiled binaries available in the Github Releases page. Otherwise, you’ll need to compile it yourself (check the instructions in the Readme). I recommend you install Amiberry in the same location for each machine, to make… Read More: (Amiberry powered) Lightwave render farm, pt 4 »
In the previous article, we talked about the different options regarding the shared content directory that we’ll be using. We will now see some example configurations and how to set them up. Scenario 1: Having the shared content directory on a Linux server This scenario also includes the case where one of the Raspberry Pi… Read More: (Amiberry powered) Lightwave render farm, pt 3 »
To make this crazy project a reality, we will need a few things. I’ve made a list of what I used and how I did it, but it may not be the best solution for everyone out there. Feel free to adapt things according to your needs and budget, of course. And in the case… Read More: (Amiberry powered) Lightwave render farm, pt 2 »
In the distant 1990, a 3D modelling, animation and raytacing package was released to the world: Lightwave 3D – it was originally running on Amigas with the Video Toaster card, but later became available as a standalone software package as well. It went on to become available to other platforms besides the Amiga as well… Read More: (Amiberry powered) Lightwave Render farm »
In the previous post, we went through the steps to download, configure and compile VBCC on Windows. It’s time to move on to the next steps. If you prefer to give up and go for the easy route, you can also download my compiled bin folder and use it. These were compiled on 2017-03-02 using Visual Studio 2017.… Read More: Setting up an Amiga Cross-Compiler (Windows) part 2 »
This is the Windows version, if you are running Linux or MacOS X, please check my other post about them here. VBCC is an excellent compiler, still actively developed and supports multiple target platforms, including our favorite Amiga (and clones). While the procedure to get it installed on Linux/Mac is rather straightforward (you have to… Read More: Setting up an Amiga Cross-Compiler (Windows) part 1 »