1FLATPAK MANIFEST(5) flatpak manifest FLATPAK MANIFEST(5)
2
6 flatpak-manifest - Information for building an application
7
9 Flatpak uses manifest, or recipe, files in a json or yaml format to
10 describe how an application and its bundled dependencies can be built
11 from sources. The manifest gets used by flatpak-builder.
12
14 The top level of the manifest file describes global attributes of the
15 application, how it can be built, and the list of modules that need to
16 be built.
17 Toplevel properties
19 These are the properties that are accepted:
20 id or app-id (string)
22 A string defining the application id.
23 branch (string)
25 The branch to use when exporting the application. If this is unset
26 the defaults come from the default-branch option.
27 This key overrides both the default-branch key, and the
29 --default-branch commandline option. Unless you need a very
30 specific branchname (like for a runtime or an extension) it is
31 recommended to use the default-branch key instead, because you can
32 then override the default using --default-branch when building for
33 instance a test build.
34 default-branch (string)
36 The default branch to use when exporting the application. Defaults
37 to master.
38 This key can be overridden by the --default-branch commandline
40 option.
41 collection-id (string)
43 The collection ID of the repository, defaults to being unset.
44 Setting a globally unique collection ID allows the apps in the
45 repository to be shared over peer to peer systems without needing
46 further configuration. If building in an existing repository, the
47 collection ID must match the existing configured collection ID for
48 that repository.
49 extension-tag (string)
51 If building an extension, the tag for the extension point to use.
52 Since flatpak 0.11.4 a runtime may define multiple locations for
53 the same extension point with the intention that different branches
54 for the extension are mounted at each location. When building an
55 extension it is necessary to know what extension point to install
56 the extension to. This option resolves any ambiguity in which
57 extension point to choose. If not specified, the default choice is
58 to install into either the only location for the extension point or
59 into the location for the untagged extension point. If there are
60 multiple locations for the same extension point defined with
61 different tags then an error will occur.
62 token-type (integer)
64 The type of token needed to install this commit. Setting this to a
65 value greater than 0 implies that authentication will be needed to
66 install the flatpak.
67 runtime (string)
69 The name of the runtime that the application uses.
70 runtime-version (string)
72 The version of the runtime that the application uses, defaults to
73 master.
74 sdk (string)
76 The name of the development runtime that the application builds
77 with.
78 var (string)
80 Initialize the (otherwise empty) writable /var in the build with a
81 copy of this runtime.
82 metadata (string)
84 Use this file as the base metadata file when finishing.
85 command (string)
87 The filename or path to the main binary of the application. Note
88 that this is really just a single file, not a commandline. If you
89 want to pass arguments, install a shell script wrapper and use that
90 as the command.
91 Also note that the command is used when the application is run via
93 flatpak run, and does not affect what gets executed when the
94 application is run in other ways, e.g. via the desktop file or
95 D-Bus activation.
96 build-runtime (boolean)
98 Build a new runtime instead of an application.
99 build-extension (boolean)
101 Build an extension.
102 separate-locales (boolean)
104 Separate out locale files and translations to an extension runtime.
105 Defaults to true.
106 id-platform (string)
108 When building a runtime sdk, also create a platform based on it
109 with this id.
110 metadata-platform (string)
112 The metadata file to use for the platform we create.
113 writable-sdk (boolean)
115 If true, use a writable copy of the sdk for /usr. Defaults to true
116 if build-runtime is specified.
117 appstream-compose (boolean)
119 Run appstream-compose during cleanup phase. Defaults to true.
120 sdk-extensions (array of strings)
122 Install these extra sdk extensions in /usr.
123 platform-extensions (array of strings)
125 Install these extra sdk extensions when creating the platform.
126 base (string)
128 Start with the files from the specified application. This can be
129 used to create applications that extend another application.
130 base-version (string)
132 Use this specific version of the application specified in base. If
133 unspecified, this uses the value specified in branch
134 base-extensions (array of strings)
136 Install these extra extensions from the base application when
137 initializing the application directory.
138 inherit-extensions (array of strings)
140 Inherit these extra extensions points from the base application or
141 sdk when finishing the build.
142 inherit-sdk-extensions (array of strings)
144 Inherit these extra extensions points from the base application or
145 sdk when finishing the build, but do not inherit them into the
146 platform.
147 tags (array of strings)
149 Add these tags to the metadata file.
150 build-options (object)
152 Object specifying the build environment. See below for details.
153 modules (array of objects or strings)
155 An array of objects specifying the modules to be built in order.
156 String members in the array are interpreted as the name of a
157 separate json or yaml file that contains a module. See below for
158 details.
159 add-extensions (objects)
161 This is a dictionary of extension objects. The key is the name of
162 the extension. See below for details.
163 add-build-extensions (objects)
165 This is a dictionary of extension objects similar to
166 add-extensions. The main difference is that the extensions are
167 added early and are available for use during the build.
168 cleanup (array of strings)
170 An array of file patterns that should be removed at the end.
171 Patterns starting with / are taken to be full pathnames (without
172 the /app prefix), otherwise they just match the basename.
173 cleanup-commands (array of strings)
175 An array of commandlines that are run during the cleanup phase.
176 cleanup-platform (array of strings)
178 Extra files to clean up in the platform.
179 cleanup-platform-commands (array of strings)
181 An array of commandlines that are run during the cleanup phase of
182 the platform.
183 prepare-platform-commands (array of strings)
185 An array of commandlines that are run after importing the base
186 platform, but before applying the new files from the sdk. This is a
187 good place to e.g. delete things from the base that may conflict
188 with the files added in the sdk.
189 finish-args (array of strings)
191 An array of arguments passed to the flatpak build-finish command.
192 rename-desktop-file (string)
194 Any desktop file with this name will be renamed to a name based on
195 id during the cleanup phase.
196 rename-appdata-file (string)
198 Any appdata file with this name will be renamed to a name based on
199 id during the cleanup phase.
200 rename-icon (string)
202 Any icon with this name will be renamed to a name based on id
203 during the cleanup phase. Note that this is the icon name, not the
204 full filenames, so it should not include a filename extension.
205 appdata-license (string)
207 Replace the appdata project_license field with this string. This is
208 useful as the upstream license is typically only about the
209 application itself, whereas the bundled app can contain other
210 licenses too.
211 copy-icon (boolean)
213 If rename-icon is set, keep a copy of the old icon file.
214 desktop-file-name-prefix (string)
216 This string will be prefixed to the Name key in the main
217 application desktop file.
218 desktop-file-name-suffix (string)
220 This string will be suffixed to the Name key in the main
221 application desktop file.
222 Build Options
224 Build options specify the build environment of a module, and can be
225 specified globally as well as per-module. Options can also be specified
226 on a per-architecture basis using the arch property.
227 These are the properties that are accepted:
229 cflags (string)
231 This is set in the environment variable CFLAGS during the build.
232 Multiple specifications of this (in e.g. per-arch area) are
233 concatenated, separated by spaces.
234 cflags-override (boolean)
236 If this is true, clear cflags from previous build options before
237 adding it from these options.
238 cppflags (string)
240 This is set in the environment variable CPPFLAGS during the build.
241 Multiple specifications of this (in e.g. per-arch area) are
242 concatenated, separated by spaces.
243 cppflags-override (boolean)
245 If this is true, clear cppflags from previous build options before
246 adding it from these options.
247 cxxflags (string)
249 This is set in the environment variable CXXFLAGS during the build.
250 Multiple specifications of this (in e.g. per-arch area) are
251 concatenated, separated by spaces.
252 cxxflags-override (boolean)
254 If this is true, clear cxxflags from previous build options before
255 adding it from these options.
256 ldflags (string)
258 This is set in the environment variable LDFLAGS during the build.
259 Multiple specifications of this (in e.g. per-arch area) are
260 concatenated, separated by spaces.
261 ldflags-override (boolean)
263 If this is true, clear ldflags from previous build options before
264 adding it from these options.
265 prefix (string)
267 The build prefix for the modules (defaults to /app for applications
268 and /usr for runtimes).
269 libdir (string)
271 The build libdir for the modules (defaults to /app/lib for
272 applications and /usr/lib for runtimes).
273 append-path (string)
275 This will get appended to PATH in the build environment (with an
276 leading colon if needed).
277 prepend-path (string)
279 This will get prepended to PATH in the build environment (with an
280 trailing colon if needed).
281 append-ld-library-path (string)
283 This will get appended to LD_LIBRARY_PATH in the build environment
284 (with an leading colon if needed).
285 prepend-ld-library-path (string)
287 This will get prepended to LD_LIBRARY_PATH in the build environment
288 (with an trailing colon if needed).
289 append-pkg-config-path (string)
291 This will get appended to PKG_CONFIG_PATH in the build environment
292 (with an leading colon if needed).
293 prepend-pkg-config-path (string)
295 This will get prepended to PKG_CONFIG_PATH in the build environment
296 (with an trailing colon if needed).
297 env (object)
299 This is a dictionary defining environment variables to be set
300 during the build. Elements in this override the properties that set
301 the environment, like cflags and ldflags. Keys with a null value
302 unset the corresponding variable.
303 secret-env (array of strings)
305 This is a array defining which host environment variables is
306 transfered to build-commands or post-install environment.
307 build-args (array of strings)
309 This is an array containing extra options to pass to flatpak build.
310 test-args (array of strings)
312 Similar to build-args but affects the tests, not the normal build.
313 config-opts (array of strings)
315 This is an array containing extra options to pass to configure.
316 secret-opts (array of strings)
318 This is an array of options that will be passed to configure, meant
319 to be used to pass secrets through host environment variables. Put
320 the option with an environment variables and will be resolved
321 beforehand. '-DSECRET_ID=$CI_SECRET'
322 make-args (array of strings)
324 An array of extra arguments that will be passed to make
325 make-install-args (array of strings)
327 An array of extra arguments that will be passed to make install
328 strip (boolean)
330 If this is true (the default is false) then all ELF files will be
331 stripped after install.
332 no-debuginfo (boolean)
334 By default (if strip is not true) flatpak-builder extracts all
335 debug info in ELF files to a separate files and puts this in an
336 extension. If you want to disable this, set no-debuginfo to true.
337 no-debuginfo-compression (boolean)
339 By default when extracting debuginfo we compress the debug
340 sections. If you want to disable this, set no-debuginfo-compression
341 to true.
342 arch (object)
344 This is a dictionary defining for each arch a separate build
345 options object that override the main one.
346 Extension
348 Extension define extension points in the app/runtime that can be
349 implemented by extensions, supplying extra files which are available
350 during runtime..
351 These are the properties that are accepted:
353 directory (string)
355 The directory where the extension is mounted. If the extension
356 point is for an application, this path is relative to /app,
357 otherwise it is relative to /usr.
358 bundle (boolean)
360 If this is true, then the data created in the extension directory
361 is omitted from the result, and instead packaged in a separate
362 extension.
363 remove-after-build (boolean)
365 If this is true, the extension is removed during when finishing.
366 This is only interesting for extensions in the add-build-extensions
367 property.
368 Additionally the standard flatpak extension properties are supported,
370 and put directly into the metadata file: autodelete, no-autodownload,
371 subdirectories, add-ld-path, download-if, enable-if, merge-dirs,
372 subdirectory-suffix, locale-subset, version, versions. See the flatpak
373 metadata documentation for more information on these.
374 Module
376 Each module specifies a source that has to be separately built and
377 installed. It contains the build options and a list of sources to
378 download and extract before building.
379 Modules can be nested, in order to turn related modules on and off with
381 a single key.
382 These are the properties that are accepted:
384 name (string)
386 The name of the module, used in e.g. build logs. The name is also
387 used for constructing filenames and commandline arguments,
388 therefore using spaces or '/' in this string is a bad idea.
389 disabled (boolean)
391 If true, skip this module
392 sources (array of objects or strings)
394 An array of objects defining sources that will be downloaded and
395 extracted in order. String members in the array are interpreted as
396 the name of a separate json or yaml file that contains sources. See
397 below for details.
398 secret-env (array of strings)
400 An array defining which host environment variables is transfered to
401 build-commands or post-install environment.
402 config-opts (array of strings)
404 An array of options that will be passed to configure
405 secret-opts (array of strings)
407 An array of options that will be passed to configure, meant to be
408 used to pass secrets through host environment variables. Put the
409 option with an environment variables and will be resolved
410 beforehand. '-DSECRET_ID=$CI_SECRET'
411 make-args (array of strings)
413 An array of arguments that will be passed to make
414 make-install-args (array of strings)
416 An array of arguments that will be passed to make install
417 rm-configure (boolean)
419 If true, remove the configure script before starting build
420 no-autogen (boolean)
422 Ignore the existence of an autogen script
423 no-parallel-make (boolean)
425 Don't call make with arguments to build in parallel
426 install-rule (string)
428 Name of the rule passed to make for the install phase, default is
429 install
430 no-make-install (boolean)
432 Don't run the make install (or equivalent) stage
433 no-python-timestamp-fix (boolean)
435 Don't fix up the *.py[oc] header timestamps for ostree use.
436 cmake (boolean)
438 Use cmake instead of configure (deprecated: use buildsystem
439 instead)
440 buildsystem (string)
442 Build system to use: autotools, cmake, cmake-ninja, meson, simple,
443 qmake
444 builddir (boolean)
446 Use a build directory that is separate from the source directory
447 subdir (string)
449 Build inside this subdirectory of the extracted sources
450 build-options (object)
452 A build options object that can override global options
453 build-commands (array of strings)
455 An array of commands to run during build (between make and make
456 install if those are used). This is primarily useful when using the
457 "simple" buildsystem. Each command is run in /bin/sh -c, so it can
458 use standard POSIX shell syntax such as piping output.
459 post-install (array of strings)
461 An array of shell commands that are run after the install phase.
462 Can for example clean up the install dir, or install extra files.
463 cleanup (array of strings)
465 An array of file patterns that should be removed at the end.
466 Patterns starting with / are taken to be full pathnames (without
467 the /app prefix), otherwise they just match the basename. Note that
468 any patterns will only match files installed by this module.
469 ensure-writable (array of strings)
471 The way the builder works is that files in the install directory
472 are hard-links to the cached files, so you're not allowed to modify
473 them in-place. If you list a file in this then the hardlink will be
474 broken and you can modify it. This is a workaround, ideally
475 installing files should replace files, not modify existing ones.
476 only-arches (array of strings)
478 If non-empty, only build the module on the arches listed.
479 skip-arches (array of strings)
481 Don't build on any of the arches listed.
482 cleanup-platform (array of strings)
484 Extra files to clean up in the platform.
485 run-tests (boolean)
487 If true this will run the tests after installing.
488 test-rule (string)
490 The target to build when running the tests. Defaults to "check" for
491 make and "test" for ninja. Set to empty to disable.
492 test-commands (array of strings)
494 Array of commands to run during the tests.
495 modules (array of objects or strings)
497 An array of objects specifying nested modules to be built before
498 this one. String members in the array are interpreted as names of a
499 separate json or yaml file that contains a module.
500 Sources
502 These contain a pointer to the source that will be extracted into the
503 source directory before the build starts. They can be of several types,
504 distinguished by the type property.
505 Additionally, the sources list can contain a plain string, which is
507 interpreted as the name of a separate json or yaml file that is read
508 and inserted at this point. The file can contain a single source, or an
509 array of sources.
510 All sources
512 only-arches (array of strings)
513 If non-empty, only build the module on the arches listed.
514 skip-arches (array of strings)
516 Don't build on any of the arches listed.
517 dest (string)
519 Directory inside the source dir where this source will be
520 extracted.
521 Archive sources (tar, zip)
523 type
524 "archive"
525 path (string)
527 The path of the archive
528 url (string)
530 The URL of a remote archive that will be downloaded. This
531 overrides path if both are specified.
532 mirror-urls (array of strings)
534 A list of alternative urls that are used if the main url fails.
535 git-init (boolean)
537 Whether to initialise the repository as a git repository.
538 archive-type (string)
540 The type of archive if it cannot be guessed from the path.
541 Possible values are "rpm", "tar", "tar-gzip", "tar-compress",
542 "tar-bzip2", "tar-lzip", "tar-lzma", "tar-lzop", "tar-xz",
543 "zip" and "7z".
544 md5 (string)
546 The md5 checksum of the file, verified after download
547 Note that md5 is no longer considered a safe checksum, we
549 recommend you use at least sha256.
550 sha1 (string)
552 The sha1 checksum of the file, verified after download
553 Note that sha1 is no longer considered a safe checksum, we
555 recommend you use at least sha256.
556 sha256 (string)
558 The sha256 checksum of the file, verified after download
559 sha512 (string)
561 The sha512 checksum of the file, verified after download
562 strip-components (integer)
564 The number of initial pathname components to strip during
565 extraction. Defaults to 1.
566 dest-filename (string)
568 Filename to for the downloaded file, defaults to the basename
569 of url.
570 Git sources
572 type
573 "git"
574 path (string)
576 The path to a local checkout of the git repository. Due to how
577 git-clone works, this will be much faster than specifying a URL
578 of file:///...
579 url (string)
581 URL of the git repository. This overrides path if both are
582 specified. When using git via SSH, the correct syntax is
583 ssh://user@domain/path/to/repo.git.
584 branch (string)
586 The branch to use from the git repository
587 tag (string)
589 The tag to use from the git repository
590 commit (string)
592 The commit to use from the git repository. If branch is also
593 specified, then it is verified that the branch/tag is at this
594 specific commit. This is a readable way to document that you're
595 using a particular tag, but verify that it does not change.
596 disable-fsckobjects (boolean)
598 Don't use transfer.fsckObjects=1 to mirror git repository. This
599 may be needed for some (broken) repositories.
600 disable-shallow-clone (boolean)
602 Don't optimize by making a shallow clone when downloading the
603 git repo.
604 disable-submodules (boolean)
606 Don't checkout the git submodules when cloning the repository.
607 Bzr sources
609 type
610 "bzr"
611 url (string)
613 URL of the bzr repository
614 revision (string)
616 A specific revision to use in the branch
617 Svn sources
619 type
620 "svn"
621 url (string)
623 URL of the svn repository, including branch/tag part
624 revision (string)
626 A specific revision number to use
627 Directory sources
629 type
630 "dir"
631 path (string)
633 The path of a local directory whose content will be copied into
634 the source dir. Note that directory sources don't currently
635 support caching, so they will be rebuilt each time.
636 skip (array of strings)
638 Source files to ignore in the directory.
639 File sources
641 type
642 "file"
643 path (string)
645 The path of a local file that will be copied into the source
646 dir
647 url (string)
649 The URL of a remote file that will be downloaded and copied
650 into the source dir. This overrides path if both are specified.
651 mirror-urls (array of strings)
653 A list of alternative urls that are used if the main url fails.
654 md5 (string)
656 The md5 checksum of the file, verified after download. This is
657 optional for local files.
658 Note that md5 is no longer considered a safe checksum, we
660 recommend you use at least sha256.
661 sha1 (string)
663 The sha1 checksum of the file, verified after download. This is
664 optional for local files.
665 Note that sha1 is no longer considered a safe checksum, we
667 recommend you use at least sha256.
668 sha256 (string)
670 The sha256 checksum of the file, verified after download. This
671 is optional for local files.
672 sha512 (string)
674 The sha512 checksum of the file, verified after download. This
675 is optional for local files.
676 dest-filename (string)
678 Filename to use inside the source dir, default to the basename
679 of path.
680 Script sources
682 This is a way to create a shell (/bin/sh) script from an inline set
683 of commands.
684 type
686 "script"
687 commands (array of strings)
689 An array of shell commands that will be put in a shellscript
690 file
691 dest-filename (string)
693 Filename to use inside the source dir, default to autogen.sh.
694 Inline data sources
696 This is a way to create a file with given contents.
697 type
699 "inline"
700 dest-filename (string)
702 Filename to use inside the source dir.
703 contents (string)
705 Text data that will be put in the file.
706 base64 (boolean)
708 Whether content is base64-encoded.
709 Shell sources
711 This is a way to create/modify the sources by running shell
712 commands.
713 type
715 "shell"
716 commands (array of strings)
718 An array of shell commands that will be run during source
719 extraction
720 Patch sources
722 type
723 "patch"
724 path (string)
726 The path of a patch file that will be applied in the source dir
727 paths (array of strings)
729 An list of paths to a patch files that will be applied in the
730 source dir, in order
731 strip-components (integer)
733 The value of the -p argument to patch, defaults to 1.
734 use-git (boolean)
736 Whether to use "git apply" rather than "patch" to apply the
737 patch, required when the patch file contains binary diffs.
738 use-git-am (boolean)
740 Whether to use "git am" rather than "patch" to apply the patch,
741 required when the patch file contains binary diffs. You cannot
742 use this at the same time as use-git.
743 options (array of strings)
745 Extra options to pass to the patch command.
746 Extra data sources
748 type
749 "extra-data"
750 filename (string)
752 The name to use for the downloaded extra data
753 url (string)
755 The url to the extra data.
756 sha256 (string)
758 The sha256 of the extra data.
759 size (number)
761 The size of the extra data in bytes.
762 installed-size (string)
764 The extra installed size this adds to the app (optional).
765
767 When building the application each command is run in a separate sandbox
768 with access to only the things required for it. This section describes
769 the details of the sandbox. Any options here can be overridden globally
770 or per-module with the build-args option (although such manifest will
771 not work if you start flatpak-builder with --sandbox).
772 Filesystem
774 Each module is built in its own build directory, stored in a sub
775 directory called build/$modulename-$count in the state dir (which is
776 typically .flatpak-builder/). Additionally there is a symlink
777 build/$modulename to the latest version. In order to generate
778 reproducible builds this directory is also mounted as
779 /run/build/$modulename in the sandbox (or
780 /run/build-runtime/$modulename when building runtimes). This is used as
781 current working directory for all build ops.
782 The destination directory for installation is accessible for writing at
784 the place it will seen at runtime. In the case of a regular application
785 this will be /app. If building a runtime it will instead be /usr, and
786 when building an extension it will be at the extensionpoint directory
787 somewhere below /app (for app extension) or /usr (for runtime
788 extensions).
789 Additionally the there will be (as needed, depending on what is
791 building) read-only mounts of the sdk at /usr, sdk extensions below
792 that, and the application at /app. No other filesystem access is
793 available.
794 Environment
796 The environment can be modified in several ways in the manifest, but
797 the default values are:
798 FLATPAK_ID
800 The id of the application currently building.
801 FLATPAK_ARCH
803 The architecture currently building.
804 FLATPAK_DEST
806 The path to where the current build should install into. This is
807 /app for application builds.
808 FLATPAK_BUILDER_N_JOBS
810 The number of jobs that flatpak-builder would normally use for make
811 -j. Defaults to ncpus unless the module disabled parallel make.
812 FLATPAK_BUILDER_BUILDDIR
814 The path to the build directory of the module currently building.
815 This is normally /run/build/$MODULE.
816 PATH
818 /app/bin:/usr/bin
819 LD_LIBRARY_PATH
821 /app/lib
822 PKG_CONFIG_PATH
824 /app/lib/pkgconfig:/app/share/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig
825 ACLOCAL_PATH
827 /app/share/aclocal
828 C_INCLUDE_PATH
830 /app/include
831 CPLUS_INCLUDE_PATH
833 /app/include
834 LDFLAGS
836 -L/app/lib
837 LC_ALL
839 en_US.utf8
840 Permissions
842 Builds have the --allow=devel and --allow=multiarch permissions that
843 regular flatpak runs don't have by default. This limits the syscall
844 filtering that is normally done so development tools like debuggers
845 work. Otherwise the build sandbox is very limited, for example there is
846 no network access.
847
849 $ flatpak-builder my-app-dir manifest.json
850 Example manifest file:
852 {
854 "id": "org.test.TestApp",
855 "runtime": "org.freedesktop.Platform",
856 "runtime-version": "1.2",
857 "sdk": "org.freedesktop.Sdk",
858 "command": "test",
859 "clean": [ "/include", "*.la" ],
860 "build-options" : {
861 "cflags": "-O2 -g",
862 "cxxflags": "-O2 -g",
863 "env": {
864 "V": "1"
865 },
866 "arch": {
867 "x86_64": {
868 "cflags": "-O3 -g",
869 }
870 }
871 },
872 "modules": [
873 {
874 "name": "pygobject",
875 "config-opts": [ "--disable-introspection" ],
876 "sources": [
877 {
878 "type": "archive",
879 "url": "http://ftp.gnome.org/pub/GNOME/sources/pygobject/2.28/pygobject-2.28.6.tar.xz",
880 "sha256": "fb8a1d4f665130a125011659bd347c7339c944232163dbb9a34fd0686577adb8"
881 },
882 {
883 "type": "patch",
884 "path": "required-pygobject-fix.patch"
885 },
886 {
887 "type": "file",
888 "path": "pygobject-extra-file",
889 "dest-filename": "extra-file"
890 }
891 ]
892 },
893 {
894 "name": "babl",
895 "build-options" : { "cxxflags": "-O2 -g -std=c++11" },
896 "cleanup": [ "/bin" ],
897 "sources": [
898 {
899 "type": "git",
900 "url": "https://gitlab.gnome.org/GNOME/babl.git"
901 }
902 ]
903 },
904 {
905 "name": "testapp",
906 "sources": [
907 {
908 "type": "bzr",
909 "url": "lp:testapp"
910 }
911 ]
912 }
913 ]
914 }
915
917 flatpak-builder(1)
918flatpak FLATPAK MANIFEST(5)