Writing Apps
Packaging
While having a build system is great, our app still isn't ready for regular users. We want to make sure our app can be built and installed without having to use Terminal. What we need to do is package our app. To do this, we use Flatpak on elementary OS. This section will teach you how to package your app as a Flatpak, which is required to publish apps in AppCenter. This will allow people to install your app and even get updates for it when you publish them.
Practice Makes Perfect
If you want to get really good really fast, you're going to want to practice. Repetition is the best way to commit something to memory. So let's recreate our entire Hello World app again from scratch:
- 1.Create a new branch folder "hello-packaging"
- 2.Set up our directory structure including the "src" and "data" folders.
- 3.Add your Copying, .desktop, .metainfo.xml, icons, and source code.
- 4.Now set up the Meson build system and translations.
- 5.Test everything!
Did you commit and push to GitHub for each step? Keep up these good habits and let's get to packaging this app!
Flatpak Manifest
The Flatpak manifest file describes your app's build dependencies and required permissions. Create a
com.github.yourusername.yourrepositoryname.yml file in your project root with the following contents:1
# This is the same ID that you've used in meson.build and other files
2
app-id: com.github.yourusername.yourrepositoryname
3
4
# Instead of manually specifying a long list of build and runtime dependencies,
5
# we can use a convenient pre-made runtime and SDK. For this example, we'll be
6
# using the runtime and SDK provided by elementary.
7
runtime: io.elementary.Platform
8
runtime-version: '6.1'
9
sdk: io.elementary.Sdk
10
11
# This should match the exec line in your .desktop file and usually is the same
12
# as your app ID
13
command: com.github.yourusername.yourrepositoryname
14
15
# Here we can specify the kinds of permissions our app needs to run. Since we're
16
# not using hardware like webcams, making sound, or reading external files, we
17
# only need permission to draw our app on screen using either X11 or Wayland.
18
finish-args:
19
- '--share=ipc'
20
- '--socket=fallback-x11'
21
- '--socket=wayland'
22
23
# This section is where you list all the source code required to build your app.
24
# If we had external dependencies that weren't included in our SDK, we would list
25
# them here.
26
modules:
27
- name: yourrepositoryname
28
buildsystem: meson
29
sources:
30
- type: dir
31
path: .
Copied!
To run a test build and install your app, we can use
flatpak-builder with a few arguments:1
flatpak-builder build com.github.yourusername.yourrepositoryname.yml --user --install --force-clean
Copied!
This tells Flatpak Builder to build the manifest we just wrote into a clean
build folder the same as we did for Meson. Plus, we install the built Flatpak package locally for our user. If all goes well, congrats! You've just built and installed your app as a Flatpak.That wasn't too bad, right? We'll set up more complicated packaging in the future, but this is all that is required to submit your app to AppCenter Dashboard for it to be built, packaged, and distributed. If you'd like you can always read more about Flatpak.
Last modified 5mo ago
Export as PDF
Copy link
Edit on GitHub