office-gobmx/distro-configs
Rene Engelhard 3e9c908b73 remove Linux ("UNX") systray "Quickstarter"
Change-Id: Ie0e8b8b7ad59ee640d6b195dfae1a7cf745056fd
Reviewed-on: https://gerrit.libreoffice.org/54543
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <Michael.Stahl@cib.de>
2018-05-23 12:02:59 +02:00
..
Jenkins
LibreOfficeAndroid.conf remove Linux ("UNX") systray "Quickstarter" 2018-05-23 12:02:59 +02:00
LibreOfficeAndroidAarch64.conf remove Linux ("UNX") systray "Quickstarter" 2018-05-23 12:02:59 +02:00
LibreOfficeAndroidX86.conf remove Linux ("UNX") systray "Quickstarter" 2018-05-23 12:02:59 +02:00
LibreOfficeCoverity.conf
LibreOfficeFlatpak.conf Adapt solenv/flatpak-manifest.in to recent download.lst changes 2018-05-15 12:14:19 +02:00
LibreOfficeHaiku.conf
LibreOfficeiOS.conf remove Linux ("UNX") systray "Quickstarter" 2018-05-23 12:02:59 +02:00
LibreOfficeLinux.conf explicitly enable avahi 2018-05-19 15:55:40 +02:00
LibreOfficeMacOSX.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.