1FLATPAK BUILD-INIT(1)         flatpak build-init         FLATPAK BUILD-INIT(1)
2
3
4

NAME

6       flatpak-build-init - Initialize a build directory
7

SYNOPSIS

9       flatpak build-init [OPTION...] DIRECTORY APPNAME SDK RUNTIME [BRANCH]
10

DESCRIPTION

12       Initializes a separate build directory.  DIRECTORY is the name of the
13       directory.  APPNAME is the application id of the app that will be
14       built.  SDK and RUNTIME specify the sdk and runtime that the
15       application should be built against and run in.  BRANCH specify the
16       version of sdk and runtime
17
18       Initializes a directory as build directory which can be used as target
19       directory of flatpak build. It creates a metadata inside the given
20       directory. Additionally, empty files and var subdirectories are
21       created.
22
23       It is an error to run build-init on a directory that has already been
24       initialized as a build directory.
25

OPTIONS

27       The following options are understood:
28
29       -h, --help
30           Show help options and exit.
31
32       --arch=ARCH
33           The architecture to use. See flatpak --supported-arches for
34           architectures supported by the host.
35
36       -v, --var=RUNTIME
37           Initialize var from the named runtime.
38
39       -w, --writable-sdk
40           Initialize /usr with a copy of the sdk, which is writable during
41           flatpak build. This can be used if you need to install build tools
42           in /usr during the build. This is stored in the usr subdirectory of
43           the app dir, but will not be part of the final app.
44
45       --tag=TAG
46           Add a tag to the metadata file. This option can be used multiple
47           times.
48
49       --sdk-extension=EXTENSION
50           When using --writable-sdk, in addition to the sdk, also install the
51           specified extension. This option can be used multiple times.
52
53       --extension=NAME=VARIABLE[=VALUE]
54           Add extension point info.
55
56       --sdk-dir
57           Specify a custom subdirectory to use instead of usr for
58           --writable-sdk.
59
60       --update
61           Re-initialize the sdk and var, don't fail if already initialized.
62
63       --base=APP
64           Initialize the application with files from another specified
65           application.
66
67       --base-version=VERSION
68           Specify the version to use for --base. If not specified, will
69           default to "master".
70
71       --base-extension=EXTENSION
72           When using --base, also install the specified extension from the
73           app. This option can be used multiple times.
74
75       --type=TYPE
76           This can be used to build different types of things. The default is
77           "app" which is a regular app, but "runtime" creates a runtime based
78           on an existing runtime, and "extension" creates an extension for an
79           app or runtime.
80
81       --extension-tag=EXTENSION_TAG
82           If building an extension, the tag to use when searching for the
83           mount point of the extension.
84
85       --verbose
86           Print debug information during command processing.
87
88       --ostree-verbose
89           Print OSTree debug information during command processing.
90

EXAMPLES

92       $ flatpak build-init /build/my-app org.example.myapp org.gnome.Sdk
93       org.gnome.Platform 3.36
94

SEE ALSO

96       flatpak(1), flatpak-build(1), flatpak-build-finish(1), flatpak-build-
97       export(1)
98
99
100
101flatpak                                                  FLATPAK BUILD-INIT(1)
Impressum