Wiki/wiki-rtd/docs/wiki_development/general/build-locally.md

Development and Build Locally Notes

This is a WIP document to help build RetroDECK locally. It is based on notes taken while adding the Ruffle(Flash Emulator) to the RetroDECK project.

Overview

RetroDECK is a big project in terms of scope and build size! The build process creates a 1.6GB flatpak file and the build folder is about 23GB. It takes about 3 hours to build on an 8 core PC.

One contributor ran into some stability problems building RetroDeck on their Linux Desktop with 16GB of ram installed. If the laptop was being used during the build it would often crash at least once. Upgrading the memory on the laptop to 32GB, not only stopped the crashes. The build process was reduced by at least 30 minutes per build too.

This document was initially based on adding a new function to RetroDECK as part of the build process. The person that wrote this as a hobbyist coder/developer, decided that it was better to cover just building RetroDECK before moving onto to adding/changing RetroDECK.

Adding to and changing the RetroDECK flatpak manifest will be covered in another wiki article.

It would also be worth running RetroDECK in debug mode to get familiar with how the /apps folder and other read only and full access areas of the flatpak work on your device. A list of the folders and file paths used by RetroDECK can be found here.

Note that you can run most applications in the app folder that have been built via flatpak.

Project Resources

In order to save project resources. Please try and use a self-hosted runner to test your build process.

Please do not forget that RetroDECK is a volunteer based open source project. If you would like to support the build environment that is provided as part of the project. Then please consider making a donation to the RetroDECk project or other projects involved.

Build Process

The build process is intensive and time consuming. About three hours on a machine with 8 cores.

From time to time to it can appear to lockup up your device especially during the build process.

Download/Clone RetroDeck

Clone the repository. The --recursive option is used to ensure the RetroDECK sub modules are download(ie Emulators from other projects). The only element that is not downloaded for changing/editing is the RetroDECK fork of ES-DE. That should only be needed if you wish to add a new emulator via ES-DE.

git clone --recursive https://github.com/XargonWan/RetroDECK

If you missed doing a recursive download then can also use the command below. The command is also initiated as part of the build process.

git submodule update --init --recursive

Then use git checkout cooker-x.x.xx to select the latest cooker branch. Tab complete should help select the version to download

You can also create your own branch with

git checkout -b branchname

Build locally via bash script

Although it possible to build via this method. Option 2 is more reliable and has more options for tracking and restarting the build if required.

Looking at the local build process is good to look at how the build process works. This helps understand the self-hosted runner option.

developer_toolbox/build_retrodeck_locally.sh

Have a look at what the script does first and look at the corresponding automation_tools/ folder that the script above references for the build

The build will take about 3 hours on an eight core pc/laptop.

Creates this folder when building locally RetroDECK/.flatpak-builder/

Produces RetroDECK-cooker.flatpak in the RetroDeck folder.

The flatpak build file can be installed/updated following this guide.

Build locally installed github runner

This section covers installing and using self-hosted github runners.

Github actions and runners

Github actions allow automated build to be created that are built via a self-hosted or hosted runner. The RetroDECK project uses self-hosted runners that can be installed on a cloud machine or a local machine.

• Advantages can Monitor, log, debug, cancel and restart. Via github app or a browser.
• Also logs progress to actions-runner/_diag/
• Greater stability for build process.

The RetroDECK project has created this Github action. You should have a cloned version of this workflow file. This file is used for cooker builds and manual builds. If you build against a cooker build it should auto build when you push your changes to your own repository.

The links provided below are for an actual build on the RetroDECK repository and give a useful view of what to expect during the build process.

Link to an actual cooker build. Link to full log off the build.

The image below shows that the build is complete and that an artifact file has been created that can be downloaded for testing. The Action also creates a local flatpak build file.

actions-runner/_work/RetroDECK/RetroDECK/RetroDECK-cooker.flatpak

Install self-hosted github runner

Add a self-hosted runner to a repository.

Setup runner to run as a service(optional)

Create the self-hosted runner as a service.

If using your own branch it can create an issue with the build process. Please refer to the RetroDECK Manifest section

On starting the build process via the runner it will create the following folder in the location you installed the self-hosted runner.

actions-runner/_work/RetroDECK/RetroDECK/

On completing the build you can use the locally produced file or download/share the artifact file produced by the self-hosted runner.

actions-runner/_work/RetroDECK/RetroDECK/RetroDECK-cooker.flatpak

RetroDECK flatpak manifest

The manifest file is what builds the application after downloads all the relevant modules and dependencies. See the Flatpak manifest guide here

For most builds you probably will not need to change the manifest file. It would need to be changed to add a new emulator or update a newer version of an emulator.

A link to the RetroDECK manifest yml can be found below. If you have download RetroDECK then it is stored here.

RetroDECK/net.retrodeck.retrodeck.yml

RetroDECK current manifest

An example of a simple build is shown below. Which downloads the Vita3K emulator latest zip and then copies/links the files for use within RetroDECK.

Please note the sha256 this is populated by this script. Which pulls in this cfg file.

If you want to add a new emulator then this also a basic/simple example how this works.

  # Vita3K - START

  - name: vita3k
    buildsystem: simple
    build-commands:
      # Copying the user icon
      - mkdir -p ${FLATPAK_DEST}/retrodeck
      - cp retrodeck.png ${FLATPAK_DEST}/retrodeck
      - unzip "ubuntu-latest.zip" -d "${FLATPAK_DEST}/share/Vita3K"
      - chmod +x "${FLATPAK_DEST}/share/Vita3K/Vita3K"
      - rm -f "${FLATPAK_DEST}/share/Vita3K/update-vita3k.sh"
      - ln -s ${FLATPAK_DEST}/share/Vita3K/Vita3K ${FLATPAK_DEST}/bin/Vita3K
    sources:
      - type: file
        url: https://github.com/Vita3K/Vita3K/releases/download/continuous/ubuntu-latest.zip
        sha256: VITA3KSHAPLACEHOLDER
      - type: file
        path: res/retrodeck.png

  # Vita3K - END

FAQ

Crash during local sh build?

• Stay Calm!
• Have you got at least 32GB of ram installed
• Wait 5 to 10 minutes and see if device starts responding again.
• Restart the PC/laptop.
• re run the command below it should hopefully continue from the last good build action.

developer_toolbox/build_retrodeck_locally.sh

Crash during local github runner build?

• Have you got at least 32GB of ram installed
• Issues with your internet connection
• Stay Calm!
• Wait 5 to 10 minutes and see if device starts responding again.
• Restart the PC/laptop.
• make sure runner started and then re run the failed Github action