Add Flatpak target and workflow #421
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Include files to generate flatpaks. libiio is compiled with -DINSTALL_UDEV_RULE=OFF and CMakeLists.txt does not install org.adi.pkexec.osc.policy file if CMAKE_INSTALL_PREFIX is /app (flatpak install prefix); this is because flatpaks run in a sandbox and its policies are defined in the main manifest file (CI/flatpak/app.yml). The flatpak was tested with org.gnome.Platform version x86_64/3.38 and x86_64/43. Signed-off-by: Jorge Marques <jorge.marques@analog.com>
Include GitHub Workflow to generate the flatpak. Uses the Flathub/Flatpak\ Builder GitHub Action. Signed-off-by: Jorge Marques <jorge.marques@analog.com>
Badge will only show status for builds at master branch. Signed-off-by: Jorge Marques <jorge.marques@analog.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Generate a flatpak package[1], as we already do with Scopy.
Flatpak policy is set in the manifest files instead of through CMake, therefore during flatpak build:
The flatpak build was tested with org.gnome.Platform version x86_64/3.38 (oldest available in flathub) and x86_64/43 (latest).
The Flathub/Flatpak Builder GitHub Action is being used,
which will pull an image from the author's account (gnome developer, flathub maintainer)
(if that's not ok, we can create our own image and publish in Docker hub, like in the others workflows).
[1] The flatpak package is available for master and flatpak branches, at flatpak build -> Summary -> Artifacts,
we also could include to the Release Assets list.
Suggestions are welcome.