d3c6ac6d0f
Just as the gtk3 plugin isn't named GNOME, rename kde5 to kf5, as it is based on the KDE frameworks 5 libraries. This also includes: * a convenience alias to load the kf5 VCL plugin in case someone requests the kde5 plugin. * keep convenience kde5 configure switch, but warn about it * rename detected desktop from kde5 to plasma5 Change-Id: I6764a05b81a5edbf284484c234fee2649aacf735 Reviewed-on: https://gerrit.libreoffice.org/75313 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de> |
||
---|---|---|
.. | ||
Jenkins | ||
LibreOfficeAndroid.conf | ||
LibreOfficeAndroidAarch64.conf | ||
LibreOfficeAndroidX86.conf | ||
LibreOfficeCoverity.conf | ||
LibreOfficeFlatpak.conf | ||
LibreOfficeHaiku.conf | ||
LibreOfficeiOS.conf | ||
LibreOfficeiOS_Sim.conf | ||
LibreOfficeLinux.conf | ||
LibreOfficeMacOSX.conf | ||
LibreOfficeOnline.conf | ||
LibreOfficeOpenBSD.conf | ||
LibreOfficeOssFuzz.conf | ||
LibreOfficeVanillaMacAppStore.conf | ||
LibreOfficeWin32.conf | ||
LibreOfficeWin64.conf | ||
README |
Pre-canned distribution configurations These files are supposed to correspond to the options used when creating the Document Foundation (or other "canonical") builds of LibreOffice for various platforms. They are *not* supposed to represent the "most useful" options for developers in general. On the contrary, the intent is that just running ./autogen.sh without any options at all should produce a buildable configuration for developers with interest in working on the most commonly used parts of the code. See [[https://wiki.documentfoundation.org/Development/ReleaseBuilds]] for how TDF builds make use of these switches. (Especially, since --with-package-format now triggers whether or not installation sets are built, all the relevant *.conf files specify it, except for LibreOfficeLinux.conf, where the TDF build instructions pass an explicit --with-package-format="rpm deb" in addition to --with-distro=LibreOfficeLinux.) (Possibly the above is a misunderstanding, or maybe there never even has been any clear consensus what situations these files actually are intended for.) The files contain sets of configuration parameters, and can be passed on the autogen.sh command line thus: ./autogen.sh --with-distro=LibreOfficeFoo Contrary to the above, in the Android case the amount of parameters you just must use is so large, that for convenience it is always easiest to use the corresponding distro-configs file. This is a bug and needs to be fixed; also configuring for Android should ideally use sane (or the only possible) defaults and work fine without any parameters at all.