summaryrefslogtreecommitdiff
path: root/meson_options.txt
Commit message (Collapse)AuthorAgeFilesLines
* build: Allow disabling GIR data generationErnestas Kulik2018-07-251-7/+74
|
* general: Assume development profile if app id is not NautilusCarlos Soriano2018-07-141-10/+1
| | | | | | | | Instead of checking explicitly for some options, we allow any value as profile and assume is a development snapshot. This will help with having Flatpak bundles/refs of different branches with different purposes.
* general: Allow running in separate instanceErnestas Kulik2018-03-181-0/+10
| | | | | | | | | | | | | | | | When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks.
* build: make all tests optionalErnestas Kulik2018-03-161-1/+1
| | | | This can help cut down on link times a bit when working on things.
* sendto-extension: move under extensions/Ernestas Kulik2018-02-091-1/+1
| | | | | | Now that the image property page is an extension, both extensions can be held under the same subdirectory. This commit also makes the image property extension optional.
* build: Set graphical tests off by defaultCarlos Soriano2018-01-301-1/+1
| | | | | | | | | | | | | | When nautilus is automatically tests we cannot assume there is a display, if we do and we run inside a displayless scenario nautilus cannot run the application and the tests fail. Graphical tests were enabled by default, but this breaks most common automatic tests scenarios, so let's disable it by default and let the developers enable if required. We should focus more in unit testing and integration tests without an actual display, and let tools like OpenQA, etc. to handle actual display testing. Alternatively we can use Xvfb to simulate a graphical env.
* build: Turn Selinux support off by defaultCarlos Soriano2018-01-301-1/+1
| | | | | | | | | | | | We were enabling Selinux support by default, which is just to show the Selinux labels in the properties dialog. However, this gives problem when trying to create a release since Flatpak Sdk doesn't have Selinux I guess to be able to work in most distros. So with the purpose of having a proper default that works in different distributions, let set it off by default.
* tests: Split between display and displaylessCarlos Soriano2018-01-061-0/+1
| | | | | | | | Some tests require gtk_init, which requires a display and therefore cannot be part of the tests to be ran in the GitLab CI. Split those so we can pass an option to meson to only test the displayless tests for GitLab CI.
* build: general cleanupsErnestas Kulik2018-01-021-15/+5
| | | | | | | | | | | | | | This commit does the following: * Canonicalize the style: * Use two-space indentations. * Un-Autotools-ify option names. * Don’t align arguments, simply increase indentation. * Don’t add a space before opening parenthesis in calls. * Remove unused variables. * Remove unused dependencies. * Remove config.h.meson. * Optimize dependencies. * Use disabler functionality for libselinux dependency, to save lines.
* general: remove desktop supportErnestas Kulik2018-01-021-3/+0
|
* general: Remove exempi and exempi-xmpCarlos Soriano2017-11-201-8/+0
| | | | Since now we use gexiv2 these are not longer necessary.
* build: Make tracker a hard dependencyBastien Nocera2017-07-181-4/+0
| | | | | | | | A large number of core features require Tracker to work, and many of the new features using Tracker don't have any fallback support, failing to build when Tracker is not available, so make tracker a hard requirement. https://bugzilla.gnome.org/show_bug.cgi?id=784940
* build: Fix tracker detectionBastien Nocera2017-07-181-2/+3
| | | | | | | Make sure that tracker-sparql is optional and auto-detected by default and that tracker-sparql-1.0 is still supported. https://bugzilla.gnome.org/show_bug.cgi?id=784940
* meson: make doc generation opt-inErnestas Kulik2017-03-011-0/+3
| | | | | | | | Since Continuous does not have GTK-Doc and jhbuild users don’t usually care about generating documentation, it makes sense to disable it by default. https://bugzilla.gnome.org/show_bug.cgi?id=779420
* general: remove empty viewErnestas Kulik2017-02-271-3/+0
| | | | | | | | Since testing is planned to be done with actual views and no one has built Nautilus with the empty view enabled recently, it is safe to say that it should go. This commit removes the empty view. https://bugzilla.gnome.org/show_bug.cgi?id=779255
* meson: don’t look for update-mime-databaseErnestas Kulik2017-02-271-3/+0
| | | | | | | | Since Nautilus no longer install a mime type (5951fadbefafd177985c824a0af7d37e5ac052c4), updating the mime database is not something that should be done anymore. https://bugzilla.gnome.org/show_bug.cgi?id=779250
* general: add support for MesonErnestas Kulik2017-02-241-0/+32
Since it’s 2017 already, Nautilus should use a build system that doesn’t take longer to set up the build than it takes to actually build. An observed build time using Ninja of roughly one-fifth of what it took Autotools is more than reason enough to add support for Meson. Along with that, this commit adds a convenience script to generate a tarball for releases, since we use libgd as a submodule and Meson does not handle source distributions. https://bugzilla.gnome.org/show_bug.cgi?id=778167
View Lorry Controller Status