Thanx Thorsten,
if so,
what are the components of cygwin which are not available on Windows itself?
Or is this (only) for historical reason when Windows support of "native"
linux tools was not as it is today?
Am 19.01.24 um 13:46 schrieb Thorsten Behrens:
Hi Joachim,
dr
Hi,
I have set up a build on Windows, following your guides. LO is built
correctly without errors and can be invoked from instdir.
But I am still confused about the LODE set up.
To build LO on windows you have to install Visual Studio with several
options about C++ and .NET Framework.
To
Hi,
I have no experience in crosscompiling. It would be a nice feature for
me, but if it is not available it is not a real problem (for me). I
don't feel confident that I can provide any helpful support on that matter.
My question was only to get some information if the crosscompiling
Hi,
Am 15.01.24 um 08:45 schrieb Miklos Vajna:
Hi Joachim,
For building on Linux for Windows: we tried that in the past (mingw) and
it didn't really work out, see core.git commit
8646ab97dc37c0606b19057686bf3d610f9c15ee (Remove MinGW support,
2017-02-10) for more details.
BTW: As far as I
is it planned to bring this on the agenda again? The mingw support was
dropped quite 7 years ago, maybe there is some progress.
On the other hand, it will come with huge amount of work, I know!
Am 15.01.24 um 08:45 schrieb Miklos Vajna:
For building on Linux for Windows: we tried that in
Hi,
building LO on Windows stops with following messages:
--snip--
[build CUT] xmlsecurity_signing2
[_RUN_] testPasswordPreserveMacroSignatureODF13::TestBody
D:/LibreOffice/lode/dev/core/xmlsecurity/qa/unit/signing/signing2.cxx:128:testPasswordPreserveMacroSignatureODF13::TestBody
It is not really straight forward to start Linux to run Windows in a VM
to work in a cygwin environment.
This is the way!
Am 15.01.24 um 08:45 schrieb Miklos Vajna:
Hi Joachim,
On Sun, Jan 14, 2024 at 05:51:20PM +0100, drei97 wrote:
Nevertheless, I am wondering if there is documentation
thanks for the information.
I am currently checking if I will be able to improve the situation. I am
interessted in contributing but if my skills are sufficient is still an
open question. Free time is another issue.
But we will see.
Am 14.01.24 um 18:07 schrieb Hossein Nourikhah:
Hello,
Hi,
may be some of you have already noticed that I am actually playing
around compiling LO as a first step.
Buildung on linux is easy, on windows more complicated. The compiler is
still running and I have no hint when it will be finished. It is
running in a VM, ...
Nevertheless, I am
I found the root cause of my problems. It sat in front of the keyboard!
LODE was not set up correctly.
The documentation was not read carefully
An autogen option (jdk-home) was wrong. The path had an "/" at the end
sh*t happens
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
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
12 matches
Mail list logo
