-
-
Notifications
You must be signed in to change notification settings - Fork 10
Buildsystem Meson
at the base will take care of processing build options defined below
Build the gresource with the various stylesheets for Jorts Application.css is generalist Themes.css is generated by stylesheet.sh (to call manually after modifications)
Skipped for windows: Builds the correct icon variant will build up metainfo, gresource, gschema, desktop according to defined constants (app name, app id, path...) will then merge the translations from po
deal with the gettext for localization, for linux builds, cascade into po/extra for the extra files (We skip appstream for windows)
will take care of setting Config.vala.in, so Vala can inherit constants set by the buildsystem (app name, app id, path...) will define the files, dependencies, and executable
variant: Define which seasonal icon to use. Ignored for windows builds, since the whole icon thing follows a different logic, and there is no update mechanism "VARIANT" flag in Vala
development: to install a dev version alongside stable one, using its own set of settings and data "DEVEL" flag in Vala
legacy-rdnn: to switch to an older app_id (as of writing this, ellie-commons for Flathub as changing to elly-code has been rejected by Flathub mods) meson will smartly switchup into the various files the correct rdnn and application path, and make both replace the other one
for windows: Meson will detect automatically if it is building for Windows, and adjust itself. No special command needed.