#BUNDLE FILES UNCOMPRESSED FULL#

For this to work, the `XMLLINT`Įnvironment variable must be set to the full path to the xmllint executable, or xmllint must be in the `PATH` otherwise the preprocessing step `xml-stripblanks` which will use the xmllint command to strip ignorable whitespace from the XML file. The only options currently supported are: Resource files can also be marked to be preprocessed, by setting the value of the `preprocess` attribute to a comma-separated list of for larger text files that are parsed once (or rarely) and then Such files will be included in the resource bundle in a compressed form, but will beĪutomatically uncompressed when the resource is used. Resource files can also be marked as compressed. Makes it easier to create relocatable applications. In memory, shared with other instances) and simple (no need to check for things like I/O errors or locate the files in the filesystem). This means that loading the resource files are efficient (as they are already You maintain the files as normal files, so its easy to edit them, but during the build the files areĬombined into a binary bundle that is linked into the executable. The Resource API and the glib-compile-resources program provide a convenient and efficient alternative to In `$datadir/appname`, or manually included as literal strings in the code. ui files, splashscreen images, GMenu markup XML, CSS files, icons, etc. Applications and libraries often contain binary or textual data that is really part of the application, rather than user data.įor instance GtkBuilder.

Bundle files uncompressed