office-gobmx/distro-configs
Luboš Luňák f4d59ec736 make Jenkins dev builds use --enable-dbgutil, not just debug
It's the "more debug" option that each developer ideally should
use unless binary compatibility is wanted. Jenkins builds done
with these settings are reportedly not published, so this is
just tinderbox builds, and there's it's better to verify
the extra dbgutil stuff too.

Change-Id: Ia2f86ff9394e155b247a6e5e1583d0681399b99b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/125381
Tested-by: Jenkins
Reviewed-by: Luboš Luňák <l.lunak@collabora.com>
2021-11-18 16:46:18 +01:00
..
Jenkins make Jenkins dev builds use --enable-dbgutil, not just debug 2021-11-18 16:46:18 +01:00
CPAndroid.conf
CPAndroidAarch64.conf
CPAndroidBranding.conf
CPAndroidX86.conf
CPAndroidX86_64.conf
LibreOfficeAndroid.conf
LibreOfficeAndroidAarch64.conf
LibreOfficeAndroidX86.conf
LibreOfficeAndroidX86_64.conf
LibreOfficeCoverity.conf a system cuckoo isn't available 2021-09-09 22:33:26 +02:00
LibreOfficeFlatpak.conf
LibreOfficeHaiku.conf
LibreOfficeiOS.conf
LibreOfficeiOS_Sim.conf
LibreOfficeLinux.conf --enable-lto for distro-configs/* that already use --enable-mergelibs 2021-10-14 15:58:07 +02:00
LibreOfficeMacOSX.conf
LibreOfficeOnline.conf --enable-lto for distro-configs/* that already use --enable-mergelibs 2021-10-14 15:58:07 +02:00
LibreOfficeOpenBSD.conf
LibreOfficeOssFuzz.conf add dbffuzzer 2021-09-25 20:25:30 +02:00
LibreOfficeVanillaMacAppStore.conf
LibreOfficeWASM32.conf
LibreOfficeWin32.conf --enable-lto for distro-configs/* that already use --enable-mergelibs 2021-10-14 15:58:07 +02:00
LibreOfficeWin64.conf --enable-lto for distro-configs/* that already use --enable-mergelibs 2021-10-14 15:58:07 +02:00
LibreOfficeWinArm64.conf --enable-lto for distro-configs/* that already use --enable-mergelibs 2021-10-14 15:58:07 +02:00
README.md

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.