forked from amazingfate/loongoffice
1e54386411
...since LO 4.1.3, cf. <http://lists.freedesktop.org/archives/libreoffice/2013-October/057006.html> "minutes of ESC call ...," and the underlying issue (Java extension's Addons.xcu causing JVM instantiation upon start of Writer on Mac) has not been addressed since, and Norbert confirmed on IRC that he did the disabling by locally specifying --disable-ext-wiki-publisher on the build machines and continues to use that configuration for all builds since (LO 4.1.4, 4.2.0, 32- and 64-bit), so better reflect that directly in distro-configs. Change-Id: Ib40588a5a6e49f7b9f58df8f1f4eb146de003444
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.