summaryrefslogtreecommitdiff
path: root/meson_options.txt
Commit message (Collapse)AuthorAgeFilesLines
* Disable granite dependency by defaultMichael Catanzaro2023-03-041-1/+1
| | | | | | | | This is probably only wanted by elementary OS and our flatpak builds. Other distros that ship Pantheon probably don't want to make Epiphany depend on Granite. Part-of: <https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/1299>
* Use Granite on elementary OSAlexander Mikhaylenko2023-03-031-0/+6
| | | | Part-of: <https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/1292>
* Require libsoup 3mcatanzaro/require-soup3Michael Catanzaro2022-06-171-6/+0
| | | | This ensures users benefit from HTTP/2 support.
* Make libportal dependency non-optionalPhaedrus Leeds2022-03-211-6/+0
| | | | | | This should simplify things since we use libportal for a few different things in ephy-flatpak-utils.c and we're about to use it in ephy-web-app-utils.c.
* Back to libsoup 2 for GNOME 41mcatanzaro/libsoup2-againMichael Catanzaro2021-07-281-1/+1
| | | | | | We will switch to libsoup 3 by default in GNOME 42 instead. https://discourse.gnome.org/t/webkit2gtk-4-1-added-to-gnome-sdk-webkit2gtk-4-0-deprecated/7053/20
* Switch to libsoup3 by defaultMichael Catanzaro2021-06-011-2/+2
| | | | | | | Our CI is not yet ready, though. We have to fix gnome-build-meta#378 first. Part-of: <https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/964>
* Add support for soup3Carlos Garcia Campos2021-04-301-0/+6
|
* Revert "Add support for soup3"Michael Catanzaro2021-04-291-6/+0
| | | This reverts commit 440fe3c55fb87aa5ad80b624984066c90e4a41a6
* Add support for soup3Carlos Garcia Campos2021-04-291-0/+6
|
* Remove enable_gsb meson optionMichael Catanzaro2021-01-071-8/+0
| | | | | | This should be a feature option, not a bool option. Anyway, it doesn't matter, since it's redundant with the API key option.
* build: Allow libportal support to be disabledwip/smcv/libportal-optionalSimon McVittie2020-10-011-0/+6
| | | | | | | | | | | | | | It isn't clear whether the API/ABI of libportal are entirely stable yet (https://github.com/flatpak/libportal/issues/33) so it is not necessarily appropriate for longer-term-supported OS distributions to include it. When building a version of epiphany for a distribution package, which is only intended to be packaged in a format other than as a Flatpak app, libportal isn't necessary anyway. libportal is also Linux-specific, so non-Linux OSs will likely want to disable it (even if it might compile successfully). Signed-off-by: Simon McVittie <smcv@debian.org>
* Add enable_gsb option to active safe browising featureJan-Michael Brummer2020-09-291-0/+7
| | | | | In case we cannot provide a gsb api key, we should disable the service entirely and hide the config option in preferences window.
* Move gsb data to meson_options.txtJan-Michael Brummer2020-09-291-0/+7
| | | | | | Move gsb_api_key to meson_options.txt so we can provide the necessary support within flatpak, but can disable it for the rest. Fixes: https://gitlab.gnome.org/GNOME/epiphany/-/issues/682
* Enable co-existing of Epiphany Tech Preview with stable versionJan-Michael Brummer2019-03-171-0/+6
| | | | Fixes: https://gitlab.gnome.org/GNOME/epiphany/issues/20
* Use feature type for meson optionsMichael Catanzaro2019-02-241-4/+4
| | | | | This could break anyone currently using -Dunit_tests=false, but probably not many people choose that.
* Don't run Safe Browsing test by defaultMichael Catanzaro2019-02-241-0/+6
| | | | | | | | Require opt-in to run network tests. Our CI has network, so we'll run it there. Fixes #684
* Use /etc/os-release to set distributor nameJan-Michael Brummer2018-12-201-6/+0
| | | | Fixes: https://gitlab.gnome.org/GNOME/epiphany/issues/586
* Remove the HTTPS Everywhere supportMichael Catanzaro2018-03-291-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | It's experimental and not supposed to be enabled, but got turned on in Arch, so best move it to a sidebranch for now. I'm not sure if we'll ever bring it back, though. HTTPS Everywhere was a great idea a few years ago, when it was common for websites to offer experimental support for HTTPS but not redirect users to it automatically. Nowadays, such websites almost always problems, such as blocked mixed content or invalid HTTPS certificates, or have disabled HTTPS since the ruleset was written. That means, to do this right, we have to ignore TLS errors -- including in subresources -- and disable mixed content blocking. This scheme to preserve web compatibility needs to be implemented before we consider bringing it back. Meanwhile, more and more websites are redirecting to HTTPS and are nowadays configured to handle this correctly, so the necessity of HTTPS Everywhere is lower now than ever before, and decreasing fast. Moreover, if a website implements its own proper support for HTTPS and starts automatically redirecting users to it, but the ruleset is not updated, then under the scheme I propose above, the ruleset would become a way of *reducing* security for websites once they've begun to support HTTPS. So I'm skeptical that we should bring this back at all. Times, they are a-changing. https://bugzilla.gnome.org/show_bug.cgi?id=794803
* Revert "Just stop running all the tests"Michael Catanzaro2018-02-221-1/+1
| | | | This reverts commit 3d674bbdf9713a2ea7bdeead6bee9e4c8e337b19.
* Just stop running all the testsMichael Catanzaro2018-02-121-1/+1
| | | | | | Probably a recipe for disaster, but half the tests are already broken and disabled, why not disable even more? But really, I just don't want to reinstall JHBuild in order to do a release.
* Add Epiphany Tech Preview brandingMichael Catanzaro2017-11-151-0/+6
| | | | | And use git describe to compute the version, so I can tell which commit I'm using.
* Rename build optionsMichael Catanzaro2017-08-301-2/+2
| | | | | | | | | | | The Meson developers have recommended that we omit enable/disable prefixes from option names, as it's redundant with the boolean value. Note that we intentionally retain underscores, rather than hyphens. There doesn't seem to be a convention for Meson, but this is suggested by the Meson documentation, looks nicer, and matches the convention in CMake world, which is the only other major build system to use -D notation for defining options.
* Disable debug goo in release modeMichael Catanzaro2017-08-301-0/+6
| | | | | All our debug stuff has been enabled in release mode since switching to meson. Time to fix that.
* meson: Remove enable_firefox_sync optionGabriel Ivascu2017-08-061-6/+0
|
* Port to meson build systemMichael Catanzaro2017-04-261-0/+23
View Lorry Controller Status