I guys,
I've already made a windows build.... using this options:
./autogen.sh \
--enable-release-build \
--enable-extra-gallery \
--enable-extra-sample \
--enable-extra-font \
--enable-extra-template \
--verbose \
--enable-verbose \
--disable-activex \
--without-junit \
--with-ant-home="/cygdrive/c/apache-ant-1.9.2/"
But now I need to add:
--with-help
--with-myspell-dicts
autogen goes ok... but when I do a:
/opt/lo/bin/make
I get the following error:
$ /opt/lo/bin/make
C:/libreoffice-4.1.0.4/bin/unpack-sources C:/libreoffice-4.1.0.4
C:/libreoffice-4.1.0.4/src/libreoffice-dictionaries-4.1.0.4.tar.xz
C:/libreoffice-4.1.0.4/src/libreoffice-help-4.1.0.4.tar.xz
Error: C:/libreoffice-4.1.0.4 is not a valid LibreOffice core source directory
make: *** [get-submodules] Error 1
So what's wrong? Why does it say it's not a core source directory? I
don't seem to find anything wrong in "bin/unpack-sources"
I really need some help here... does anyone have any clues?
Thanks
*Flávio Moringa*
Project Leader
Caixa Mágica Software
Energia Open Source
Rua Soeiro Pereira Gomes, Lote 1 - 4.º B,
Edifício Espanha, 1600-196 Lisboa - Portugal
Tel.: +351 217 921 260 Fax: +351 217 921 261
http://www.caixamagica.pt
https://twitter.com/flaviomoringa
https://www.facebook.com/flaviomoringa<https://www.facebook.com/flavio.moringa>
http://pt.linkedin.com/in/flaviomoringa
http://people.caixamagica.pt/flaviomoringa
Context
- URGENT: Build fails when --with-help is enabled · Flavio Moringa
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.