Jump to content

Get Involved/development/More: Difference between revisions

From KDE Community Wiki
Nmariusp (talk | contribs)
Add docker
 
Nmariusp (talk | contribs)
This paged is not meant for people that are starting to program for KDE
Line 1: Line 1:
This page is the continuation with more advanced topics of the page [[Get_Involved/development]].
This paged is not meant for people that are starting to program for KDE.
== Develop in a Linux container ==
== Develop in a Linux container ==



Revision as of 02:12, 24 December 2022

This page is the continuation with more advanced topics of the page Get_Involved/development.

This paged is not meant for people that are starting to program for KDE.

Develop in a Linux container

When you start programming for KDE, it is recommended that you use kdesrc-build in your main operating system or in a virtual machine running on a rolling-release Linux distribution (Arch, openSUSE Tumbleweed, KDE neon) or running on e.g. the latest version of Fedora KDE Spin or Kubuntu.

As an alternative, you can run kdesrc-build in a Linux container (docker, podman, toolbx, distrobox).

Option 1. The KDE PIM Docker image

You can install Docker and the KDE PIM Docker image. It provides a development environment that is isolated from your day-to-day system. It is based on KDE Neon Unstable.

Option 2. distrobox

Or, you can just create a long lived (pet not cattle) container using distrobox and podman (or docker). See https://www.youtube.com/watch?v=9JEALbcmcCg https://github.com/89luca89/distrobox

Start with the official Docker hub container image of one of the Linux distributions that is better suited for kdesrc-build. Then setup kdesrc-build in the container. distrobox makes it such that you can run GUI apps in the container. Also, your user's home directory (~) is the same in the host operating system and in the container. Warning: the container will write to your home directory and may conflict with your host operating system.