-
I would prefer to use nvim over Builder. With the template app I used I have been trying to just manually copy them to the .build folder but I am not able to get incremental builds working this way. I have put in a couple hours trying to get this working so I thought I should probably reach out instead. Is there a command for flatpak-builder that just uses the current directory as build dir or is GNOME Builder using something different? Any info is greatly appreciated as I am new to flatpak. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Okay after some more experimentation and research I landed on this manifest {
...
"build-options": {
...
"build-args": [
"--share=network"
"--build-dir=<<PROJ_DIR>>",
"--filesystem=<<PROJ_DIR>>",
],
"env": {
"FLATPAK_BUILDER_BUILDDIR": "<<PROJ_DIR>>"
}
},
This allows for incremental builds but not LSP support. I currently have this set in a Makefile debug:
@flatpak-builder .build/flatpak-builder debug.me.amzd.Recommended.json --force-clean --install --user
@flatpak run me.amzd.Recommended
release:
@flatpak-builder .build/flatpak-builder me.amzd.Recommended.json --force-clean --install --user
install_dependencies:
@flatpak install org.freedesktop.Sdk.Extension.swift5 |
Beta Was this translation helpful? Give feedback.
Okay after some more experimentation and research I landed on this manifest
--share=network
because SPM needs to fetch dependencies (you can omit this if you runswift package resolve
manually)--filesystem=
gives the build system access to project files instead of only /run/build/proj--build-dir=
makes sure theswift build
command is run inside the project folder instead of the sandboxed /run/build/projFLATPAK_BUILDER_BUILDDIR
by defaultflatpack-builder
set…