office-gobmx/distro-configs
Stephan Bergmann fc1e12bb2d distro-configs/LibreOfficeFlatpak.conf lacks --without-system-java-websocket
...after 3de3f660af "add a
--with-system-java-websocket"

Change-Id: If96dafacbc33746934a2d388b11436c797290559
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/177275
Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de>
Tested-by: Jenkins
2024-11-25 18:24:40 +01:00
..
Jenkins
CPAndroid.conf
CPAndroidAarch64.conf
CPAndroidBranding.conf
CPAndroidX86.conf
CPAndroidX86_64.conf
CPLinux-LOKit.conf
LibreOfficeAndroid.conf
LibreOfficeAndroidAarch64.conf
LibreOfficeAndroidX86.conf
LibreOfficeAndroidX86_64.conf
LibreOfficeCoverity.conf
LibreOfficeFlatpak.conf
LibreOfficeHaiku.conf
LibreOfficeiOS.conf
LibreOfficeiOS_Sim.conf
LibreOfficeLinux.conf
LibreOfficeMacOSX.conf
LibreOfficeOnline.conf
LibreOfficeOpenBSD.conf
LibreOfficeOssFuzz.conf
LibreOfficeVanillaMacAppStore.conf
LibreOfficeWASM32.conf
LibreOfficeWin32.conf
LibreOfficeWin64.conf
LibreOfficeWinArm64.conf
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.