summaryrefslogtreecommitdiff
path: root/build-aux
Commit message (Collapse)AuthorAgeFilesLines
* dist: Fix css theme disting after HighContrast-dark changeswip/kalev/dist-HighContrast-darkKalev Lember2021-01-191-1/+1
| | | | | Commit f60d245e327a760a188e8b5a40844f5fe092df43 renamed it from HighContrast-inverse.css to HighContrast-dark.css.
* dist: Add a dist script to generate cssMatthias Clasen2021-01-121-0/+19
| | | | | | When I added the sassc option, I failed to ensure that the theme css is included in the tarballs. This is required to make tarball builds with -Dsassc=disabled work.
* Call the newly installed gtk4-update-icon-cacheebassi/issue-3495Emmanuele Bassi2020-12-201-23/+25
| | | | Otherwise we rely on whatever it's inside the PATH.
* flatpak: builder optionsJakub Steiner2020-08-133-66/+102
| | | | - avoid vulkan from crashing the inspector
* Adwaita: sidebar color for file pickerJakub Steiner2020-07-131-31/+45
| | | | | | - avoid using the selected blue for the sidebar Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/1586
* build-aux: fallback to default glib-compile-schemas & gio-querymodules.Jehan2020-06-281-0/+6
| | | | | | The pkg-config variables have been added in GLib 2.62.0. Let's fallback to default names for these tools in such case (`pkg-config` still returns a 0 return value, but with empty output for absent variables).
* build-aux: search various Glib/GIO utilities in .pc file.Jehan2020-06-281-3/+9
| | | | | | | Some distributions are renaming Glib/GIO utilities for multi-arch reasons so pkg-config variables have been added to find the correct name of a tool. GTK+ should use these variables instead of searching in PATH. See glib#1796.
* flatpak: Build against the master runtimeMatthias Clasen2020-02-071-1/+1
| | | | | This is what the ci is set up to use, and building against 3.34 fails there.
* Build sassc as a dependency for flatpaksMatthias Clasen2020-02-063-1/+91
| | | | | | | Downloading the subproject during the GTK build fails in a flatpak build due to lack of network access. flatpak-builder insists on having these things explicitly spelled out as dependencies.
* Add a flatpak manifest for org.gtk.IconBrowser4Matthias Clasen2019-04-021-0/+72
| | | | And build it in ci.
* flatpaks: Drop dconf permissionsMatthias Clasen2019-04-022-6/+4
| | | | | | | | We are building against the 3.32 sdk, which has a new-enough glib to default to the keyfile settings backend. Also, use fallback-x11, so we prefer Wayland.
* widget-factory: Rename to org.gtk.WidgetFactory4Matthias Clasen2019-04-021-1/+1
|
* gtk-demo: Rename to org.gtk.Demo4Matthias Clasen2019-04-021-1/+1
|
* post-install: Use gtk4-update-icon-cacheMatthias Clasen2019-04-021-1/+1
| | | | | | I was building GTK in a minimal container without GTK3 installed, and this caused install to fail. We should use the tool that we just installed.
* build: use condense the mkdir calls to onelinersJordan Petridis2019-02-271-4/+2
|
* build: no need to replace path separatorsJordan Petridis2019-02-271-2/+2
| | | | Python APIs accept both `\` and `/` as path separators.
* build: Use python3 for the post install scriptJordan Petridis2019-02-271-1/+1
| | | | | | | | | While *some* systems alias python to python3 nowdays, this is not true for eveything. Especially systems that can potentially offer both python2 and python3. According to both PEP 394 and PEP 441 its recommended to always add the 3 in the shebang.
* Merge branch 'wip/fanc999/meson.msvc' into 'master'Chun-wei Fan2019-02-232-26/+33
|\ | | | | | | | | GTK+ 4: Improve Windows/Visual Studio build experience See merge request GNOME/gtk!185
| * build: Make post-install script a Python scriptChun-wei Fan2018-12-062-26/+33
| | | | | | | | | | | | | | | | | | | | The existing post-install shell script will most likely not work on Visual Studio builds as there is normally no shell interpreter installed on the system where the build is done, but the build is normally done in a standard Windows cmd.exe console. Instead, use a Python script so that it will work on the platforms that Python supports.
* | flatpak: Stop renaming iconsMatthias Clasen2019-02-092-2/+0
|/ | | | | | | We are now installing properly named icons, no need to rename anymore. This was causing ci to fail.
* demos: Make desktop file names match the application idGuido Günther2018-08-022-2/+0
|
* ci: Disable tests when building GrapheneEmmanuele Bassi2018-05-082-2/+6
| | | | | | | | Our flatpak-builder manifests include building Graphene from Git; since we're building the GTK demos, it's pointless to build the Graphene tests as well. Disabling tests and benchmarks avoids pointless installations inside the Flatpak build repo that will just be removed by the time we bundle the demo.
* flatpak: Bundle wayland for nowMatthias Clasen2018-04-152-0/+28
| | | | | We need a newer wayland than is available in the runtime currently, so use the power of flatpak and bundle it.
* Add flatpak builder manifests for our demosEmmanuele Bassi2018-03-202-0/+118
| | | | | We can use manifests as targets when building GTK inside a flatpak environment; or we can use them for CI purposes.
* Use gio-querymodulesMatthias Clasen2018-03-061-0/+8
| | | | | | | GIO has this facility, so we should use it. At the same time, make sure the immodules directory exists, even if we don't install any modules there outselves.
* Convert immodules to use an extension pointMatthias Clasen2018-02-241-5/+0
| | | | | | | | | | | Add an extension point called gtk-im-module, which requires the type GtkIMContext. Simplify the loading by using GIO infrastructure. Drop the locale filtering for now, I don't think it is really necessary nowadays. Convert existing platform modules to gio modules. Sill to do: Drop the conditional build machinery. Either always include them, or never.
* build: Create input method module cache directoryDaniel Stone2018-02-051-1/+3
| | | | | | | | Before running gtk-query-immodules, the cache output directory may not actually exist. Make sure it does before we try to write into it. https://bugzilla.gnome.org/show_bug.cgi?id=793182 Signed-off-by: Daniel Stone <daniels@collabora.com>
* build: Fix post-install scriptEmmanuele Bassi2017-08-141-2/+2
| | | | | Use the appropriate variable when expanding the input method modules path.
* build: Add post-install scriptEmmanuele Bassi2017-05-031-0/+21
When building GTK+ straight from the repository without any assistance from packaging tools, we need to trigger system-wide updates, like the icon theme cache update, or the schema compilation.
View Lorry Controller Status