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


Thanks a lot... I figured it out..  I had to update Microsoft Visual Studio
to include .NET desktop development and. NET Core cross-platform
development.

On Sat, 4 Jul, 2020, 3:12 PM Jan-Marek Glogowski, <glogow@fbihome.de> wrote:

Please keep the list as CC, so others can follow the conversation and
reply.

Am 04.07.20 um 10:55 schrieb anshu khare:
I followed this documentation
https://wiki.documentfoundation.org/Development/BuildingOnWindows

On running

 /cygdrive/c/sources/libo-core/autogen.sh \
               --with-external-tar=/cygdrive/c/sources/lo-externalsrc \
               --with-junit=/cygdrive/c/sources/junit-4.10.jar \
               --with-ant-home=/cygdrive/c/sources/apache-ant-1.9.5 \

--enable-pch --disable-ccache \
in the Cygwin shell, I get the following error:

checking for al.exe... configure: error: al.exe not found as /al.exe
Error running configure at /cygdrive/c/sources/libo-core/autogen.sh line
299.

Please re-check the installed MSVS 2019 components listed in the
article. al.exe is supposed to be part of the ".NET Framework SDK",
which should always be installed AFAIK. LO supports v4.6 to v4.8, which
seems to include all versions installable by the MSVS installer.

If the ".NET Framework SDK" is installed, I suggest to ask on IRC for
further help debugging the problem. I guess analyzing this case will
become much more complicated.

Jan-Marek


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.