office-gobmx/distro-configs
Stephan Bergmann 8fc7e560db Make building installation sets depend on --with-package-format=...
...instead of inconsitently having it depend on --enable-epm for some platforms
and having it always enabled on Windows.  Only Android and iOS are presumably
still special and build any installation sets in their specific modules and
outside instsetoo_native.

One consequence is that for a non-Windows --enable-online-update
--without-package-format build, instdir's version ini-file contains an
UpdateURL that ends in just "?pkgfmt=" without an actual format identifier.
However, checking whether the update feature would actually work is difficult
for most such developer builds, anyway.

Change-Id: If14fcf0b2e612499811e8a6e067a854bda612c42
2013-10-15 17:57:16 +02:00
..
LibreOfficeAndroid.conf
LibreOfficeAndroidX86.conf
LibreOfficeiOS.conf
LibreOfficeLinux.conf
LibreOfficeMacOSX.conf
LibreOfficeMinGW.conf
LibreOfficeMinGW64.conf
LibreOfficeOpenBSD.conf
LibreOfficeWin32.conf
LibreOfficeWin64.conf
OxygenOfficeLinux.conf
OxygenOfficeWin32.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 wihout any
parameters at all.