On 14.1.2024 12.16, jh276 wrote:
Am 14.01.24 um 10:28 schrieb drei97:
Why then no autogen.input is created, I don't know
Am 14.01.24 um 08:20 schrieb Ilmari Lauhakangas:
On 13.1.2024 19.24, y27p6e3vu...@web.de wrote:
If you had used the LODE method, an autogen.input file would have been
crea
autogen.sh is now running even with none existing autogen.input.
Am 14.01.24 um 10:28 schrieb drei97:
I had used LODE.
the important part is:
"The Easiest way to perform the following is to use LODE, which
automates all that is necessary, beyond installing Visual Studio and
Java" ;-)
Why
I had used LODE.
the important part is:
"The Easiest way to perform the following is to use LODE, which
automates all that is necessary, beyond installing Visual Studio and
Java" ;-)
Why then no autogen.input is created, I don't know
Am 14.01.24 um 08:20 schrieb Ilmari Lauhakangas:
On 13
It is really hard to get all which is necessary and quite easy to miss
important information. The information about the VS option is some line
behind the step to run autogen.sh.
I got stuck with JDK and did not proceed in reading the docs further.
Thanks for pointing out.
Am 14.01.24 um 05:2
On 13.1.2024 19.24, y27p6e3vu...@web.de wrote:
Hi,
I am trying to compile LO for the first time on windows and do follow
the official guide
https://wiki.documentfoundation.org/Development/BuildingOnWindows
Nevertheless I am runnning into several issues while configuring the build.
Running autog
On 1/13/2024 11:24 PM, y27p6e3vu...@web.de wrote:
it is not finding C++ build tools (Win 10 SDK), even if Visual Studio is
available. I have to use the option "--with-visual-studio=2022"
Yes, it is expected and normal. We keep the baseline at VS 2019 level
[1] (IIUC, this is what the official
