Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi all, I'm trying to get into being able to help contribute code to
LibreOffice, starting by building LibreOffice on Windows, using
Cygwin. I've been following the wiki pages
https://wiki.documentfoundation.org/Development/BuildingOnWindows and
https://wiki.documentfoundation.org/Development/Windows_Build_Dependencies
I've gotten as far as trying to run autogen.sh for the first time,
with the following error when running configure at autogen.sh line
209: "configure: error: invalid feature name: atl"
I have VS2012 Express, so I know that ATL should be disabled. I
included that command when I run autogen.sh. It doesn't pass it along
to configure, and when I added it to default.conf to make it pass it,
it had no effect (same error occurred).
Can someone tell me what I'm doing wrong?

$   ../core/autogen.sh \
               --with-external-tar=../opt \
               --with-junit=../opt/junit-4.10.jar \
               --with-ant-home=../opt/apache-ant-1.9.2 \
               --enable-pch --disable-ccache \
               --disable-activex --disable-atl
../core/autogen.sh: line 1: $':\r': command not found
Running ./configure with '--with-external-tar=../opt'
'--with-junit=../opt/junit-4.10.jar'
'--with-ant-home=../opt/apache-ant-1.9.2' '--enable-pch' '--disable-c'
'--srcdir=/cygdrive/c/libreoffice/core'
'--enable-option-checking=fatal'
configure: error: invalid feature name: atl
Error running configure at ../core/autogen.sh line 209.

Context


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.