Re: Official support for windows-arm64
On 3/22/24 21:45, Thorsten Behrens wrote: Hi Pierrick, Pierrick Bouvier wrote: Does any one of you has this responsibility in the project? Or can you point me someone to contact? If nobody else wants to jump in - we're happy to host a box (details TBD, but in any case Stephan will need more or less direct access). There's also the option that TDF hosts machines, but depending on whether they're rack-mountable & have iLO, perhaps having them physically sitting on the developer desk has a number of upsides... ;) It's not a rack-mountable machine (search for "Windows dev kit 2023"), but it's pretty small (similar to a mac mini). So if that's fine for you (and there's no concerns from the project), let's discuss further details for such a loan 1:1? Okay, I'll start a thread with people from MS and you, so you can discuss directly with them. Cheers, Thorsten Thanks, Pierrick
Re: Official support for windows-arm64
Hi Pierrick, Pierrick Bouvier wrote: > Does any one of you has this responsibility in the project? > Or can you point me someone to contact? > If nobody else wants to jump in - we're happy to host a box (details TBD, but in any case Stephan will need more or less direct access). There's also the option that TDF hosts machines, but depending on whether they're rack-mountable & have iLO, perhaps having them physically sitting on the developer desk has a number of upsides... ;) So if that's fine for you (and there's no concerns from the project), let's discuss further details for such a loan 1:1? Cheers, Thorsten -- Thorsten Behrens Managing Director ––– allotropia software GmbH Versmannstr. 4 20457 Hamburg Germany ––– https://www.allotropia.de ––– Registered office: Hamburg, Germany Registration court Hamburg, HRB 165405 Managing director: Thorsten Behrens VAT-ID: DE 335606919 ––– signature.asc Description: PGP signature
Re: Official support for windows-arm64
Hi everyone, after discussing with our contact in Microsoft, they are willing to help on this. Now, we need someone to contact to discuss this, see where machines would be hosted, and how we can arrange shipment. Does any one of you has this responsibility in the project? Or can you point me someone to contact? Don't hesitate to send a private email if you don't wan't this to go publicly. Regards, Pierrick On 3/19/24 13:20, Pierrick Bouvier wrote: On 3/15/24 18:12, Thorsten Behrens wrote: Hi Pierrick, Christian Lohmaier wrote: and we discussed that with Microsoft, which could sponsors up to two (physical) machines for this. Let us know how we can help! Thanks for the offer, now the hard part begins: Finding people with the required skills to make use of that ;-) Provided there's some easy access to native ARM hardware, Stephan (in Cc) would be interested in prodding the bridge problem a bit. I'd be happy to fund at least the engineering hours for a while. That's awesome! I'll discuss this with our contact at Microsoft, to see how we can arrange access to those machines as soon as possible. Regards, Pierrick Cheers, Thorsten
Re: Official support for windows-arm64
On 3/15/24 18:12, Thorsten Behrens wrote: Hi Pierrick, Christian Lohmaier wrote: and we discussed that with Microsoft, which could sponsors up to two (physical) machines for this. Let us know how we can help! Thanks for the offer, now the hard part begins: Finding people with the required skills to make use of that ;-) Provided there's some easy access to native ARM hardware, Stephan (in Cc) would be interested in prodding the bridge problem a bit. I'd be happy to fund at least the engineering hours for a while. That's awesome! I'll discuss this with our contact at Microsoft, to see how we can arrange access to those machines as soon as possible. Regards, Pierrick Cheers, Thorsten
Re: Official support for windows-arm64
On 3/15/24 15:08, Christian Lohmaier wrote:
Hi Pierrick, *,
On Fri, Mar 15, 2024 at 11:41 AM Pierrick Bouvier
wrote:
I would like to discuss and offer some help on support for windows-arm64
platform.
That's great to hear!
Linaro, through the Windows on Arm
(https://www.linaro.org/windows-on-arm/) team, has been supporting
various open source projects to enable them on windows-arm64. In
collaboration with Microsoft, we would like to help LibreOffice to offer
stable builds for this platform.
Sounds great!
So far, I've been able to reproduce existing cross compilation build,
thanks to work merged in LibreOffice 7.1. We noticed the existence of
experimental installers, built on a daily basis
(https://ci.libreoffice.org//job/lo_daily_tb_win_arm64/).
We also have installers for all officially released versions e.g.
https://download.documentfoundation.org/libreoffice/stable/24.2.1/win/aarch64/
or
https://download.documentfoundation.org/libreoffice/stable/7.6.5/win/aarch64/
But we don't offer it on our download-pages because we're having bugs
in our bridges code that causes a crash when loading writing aids
using python (or when you try to run python or java macros, i.e. stuff
that uses the bridge code).
We noticed that the lack of available machines for this platform could
be a problem,
Yeah, while cross-compiling is not a problem, actually running it and
debugging the problem is not possible without the real hardware.
If you already built LibreOffice on arm, you can test/trigger the
bridges issue with e.g. a VSCode style launch task that would look
something like this
"program": "C:/cygwin64/home/lohma/build/instdir/program/uno.exe",
"args": ["-s", "com.sun.star.test.bridge.BridgeTest", "--",
"com.sun.star.test.bridge.CppTestObject",
"-env:LO_BUILD_LIB_DIR=file:///$W/LinkTarget/Library",
"-env:URE_MORE_SERVICES=file:///$W/Rdb/uno_services.rdb",
"-env:URE_MORE_TYPES=file:///$W/UnoApiTarget/bridgetest.rdb"
"environment": [
{ "name": "W",
"value": "C:/cygwin64/home/lohma/build/workdir"
}]
That is running the basic bridges test for the c++ bridge in isolation
(defined in testtools/CustomTarget_uno_test.mk - "make check" would
also run this one)
The code for the c++ uno bridge is in bridges/source/cpp_uno and
there's a basic description of UNO and description of the interface
proxies at
https://wiki.documentfoundation.org/Documentation/DevGuide/Advanced_UNO
- albeit a bit dated)
The bridges code uses assembler to for passing stuff around between
the runtimes and do type matching, and somewhere in there is a bug -
might be an alignment issue but I so far just lacked the skills to
look at it/the time to require the necessary skills...
and we discussed that with Microsoft, which could sponsors
up to two (physical) machines for this.
Let us know how we can help!
Thanks for the offer, now the hard part begins: Finding people with
the required skills to make use of that ;-)
Thanks for your encouraging answer!
With the answer from Thorsten, it seems like we could have a nice
solution to support this platform.
I'll loop this with our contact at Microsoft, and see how it could be
possible to send machines.
Regards,
Pierrick
ciao
Christian
Re: Official support for windows-arm64
And even if it was - a change in the buildsystem (be it cmake, meson or whatever else) doesn't change that architecture-specific *code* (or compiler options, for some matters) needs to be changed. Build system stuff doesn't change that. That is completely clear to me. But if cmake for windows is even portet to arm, it should be easier to work with on arm for windows arm architecture. But anyway, I'll shut up now.
Re: Official support for windows-arm64
Hi, Am 16.03.24 um 17:23 schrieb Sophia Schröder: then I probably misunderstood the ESC minutes from 2024/02/29: Yes. + cmake find modules for SDK examples (Hossein) + Set of patches from Konstantin (WIP) https://gerrit.libreoffice.org/c/core/+/162978 + Similar structure is needed for qmake That is solely for the examples shipped in the SDK. Not for LO itself. And even if it was - a change in the buildsystem (be it cmake, meson or whatever else) doesn't change that architecture-specific *code* (or compiler options, for some matters) needs to be changed. Build system stuff doesn't change that. Regards, Rene
Re: Official support for windows-arm64
Hi Ilmary, then I probably misunderstood the ESC minutes from 2024/02/29: + cmake find modules for SDK examples (Hossein) + Set of patches from Konstantin (WIP) https://gerrit.libreoffice.org/c/core/+/162978 + Similar structure is needed for qmake + would this mean duplicated build systems for each example? (Miklos) + for each example, the maintenance would be low, hopefully (Hossein) + would be the goal to have old/cmake/qmake, 3 parallel build systems? (Miklos) + yes, for now (Hossein) + the cmake part for each example is small + smells like explosion of combinatorics (Stephan) + would be careful before going down that road + if the end goal is to settle down on cmake, love it (Thorsten) + but 3 in the long run is far from ideal. + cmake is not that exotic, we require it already for doxygen (Miklos) + which makes it supported on CI already (Thorsten) + if interested in doing the work + update the docs, then why not, as long as it's a single build system (Stephan) + but then do avoid qmake, and do switch over from gmake at the end + avoids the exploson Sorry for the noise Am 16.03.24 um 17:18 schrieb Ilmari Lauhakangas: On 16.3.2024 17.41, Sophia Schröder wrote: Hi all, Just a side note from a community member: I don't know how much the hassle and the costs are, but LibreOffice wants to switch to Cmake anyway. (I saw Cmake mentioned at Linaro's webpage). There has been quite a lot of work toward building LibreOffice with Meson. There has not been discussion about investing time into building with CMake. Ilmari
Re: Official support for windows-arm64
On 16.3.2024 17.41, Sophia Schröder wrote: Hi all, Just a side note from a community member: I don't know how much the hassle and the costs are, but LibreOffice wants to switch to Cmake anyway. (I saw Cmake mentioned at Linaro's webpage). There has been quite a lot of work toward building LibreOffice with Meson. There has not been discussion about investing time into building with CMake. Ilmari
Re: Official support for windows-arm64
Hi all, Just a side note from a community member: I don't know how much the hassle and the costs are, but LibreOffice wants to switch to Cmake anyway. (I saw Cmake mentioned at Linaro's webpage). Probably we can kill several birds with one stone. Or at least can do some steps in that direction... Am 15.03.24 um 15:12 schrieb Thorsten Behrens: Hi Pierrick, Christian Lohmaier wrote: and we discussed that with Microsoft, which could sponsors up to two (physical) machines for this. Let us know how we can help! Thanks for the offer, now the hard part begins: Finding people with the required skills to make use of that ;-) Provided there's some easy access to native ARM hardware, Stephan (in Cc) would be interested in prodding the bridge problem a bit. I'd be happy to fund at least the engineering hours for a while. Cheers, Thorsten Cheers, Sophia
Re: Official support for windows-arm64
Hi Pierrick, Christian Lohmaier wrote: > > and we discussed that with Microsoft, which could sponsors > > up to two (physical) machines for this. > > > > Let us know how we can help! > > Thanks for the offer, now the hard part begins: Finding people with > the required skills to make use of that ;-) > Provided there's some easy access to native ARM hardware, Stephan (in Cc) would be interested in prodding the bridge problem a bit. I'd be happy to fund at least the engineering hours for a while. Cheers, Thorsten -- Thorsten Behrens Managing Director ––– allotropia software GmbH Versmannstr. 4 20457 Hamburg Germany ––– https://www.allotropia.de ––– Registered office: Hamburg, Germany Registration court Hamburg, HRB 165405 Managing director: Thorsten Behrens VAT-ID: DE 335606919 ––– signature.asc Description: PGP signature
Re: Official support for windows-arm64
Hi Pierrick, *,
On Fri, Mar 15, 2024 at 11:41 AM Pierrick Bouvier
wrote:
>
> I would like to discuss and offer some help on support for windows-arm64
> platform.
That's great to hear!
> Linaro, through the Windows on Arm
> (https://www.linaro.org/windows-on-arm/) team, has been supporting
> various open source projects to enable them on windows-arm64. In
> collaboration with Microsoft, we would like to help LibreOffice to offer
> stable builds for this platform.
Sounds great!
> So far, I've been able to reproduce existing cross compilation build,
> thanks to work merged in LibreOffice 7.1. We noticed the existence of
> experimental installers, built on a daily basis
> (https://ci.libreoffice.org//job/lo_daily_tb_win_arm64/).
We also have installers for all officially released versions e.g.
https://download.documentfoundation.org/libreoffice/stable/24.2.1/win/aarch64/
or
https://download.documentfoundation.org/libreoffice/stable/7.6.5/win/aarch64/
But we don't offer it on our download-pages because we're having bugs
in our bridges code that causes a crash when loading writing aids
using python (or when you try to run python or java macros, i.e. stuff
that uses the bridge code).
> We noticed that the lack of available machines for this platform could
> be a problem,
Yeah, while cross-compiling is not a problem, actually running it and
debugging the problem is not possible without the real hardware.
If you already built LibreOffice on arm, you can test/trigger the
bridges issue with e.g. a VSCode style launch task that would look
something like this
"program": "C:/cygwin64/home/lohma/build/instdir/program/uno.exe",
"args": ["-s", "com.sun.star.test.bridge.BridgeTest", "--",
"com.sun.star.test.bridge.CppTestObject",
"-env:LO_BUILD_LIB_DIR=file:///$W/LinkTarget/Library",
"-env:URE_MORE_SERVICES=file:///$W/Rdb/uno_services.rdb",
"-env:URE_MORE_TYPES=file:///$W/UnoApiTarget/bridgetest.rdb"
"environment": [
{ "name": "W",
"value": "C:/cygwin64/home/lohma/build/workdir"
}]
That is running the basic bridges test for the c++ bridge in isolation
(defined in testtools/CustomTarget_uno_test.mk - "make check" would
also run this one)
The code for the c++ uno bridge is in bridges/source/cpp_uno and
there's a basic description of UNO and description of the interface
proxies at
https://wiki.documentfoundation.org/Documentation/DevGuide/Advanced_UNO
- albeit a bit dated)
The bridges code uses assembler to for passing stuff around between
the runtimes and do type matching, and somewhere in there is a bug -
might be an alignment issue but I so far just lacked the skills to
look at it/the time to require the necessary skills...
> and we discussed that with Microsoft, which could sponsors
> up to two (physical) machines for this.
>
> Let us know how we can help!
Thanks for the offer, now the hard part begins: Finding people with
the required skills to make use of that ;-)
ciao
Christian
Official support for windows-arm64
Dear LibreOffice developers, I would like to discuss and offer some help on support for windows-arm64 platform. Linaro, through the Windows on Arm (https://www.linaro.org/windows-on-arm/) team, has been supporting various open source projects to enable them on windows-arm64. In collaboration with Microsoft, we would like to help LibreOffice to offer stable builds for this platform. So far, I've been able to reproduce existing cross compilation build, thanks to work merged in LibreOffice 7.1. We noticed the existence of experimental installers, built on a daily basis (https://ci.libreoffice.org//job/lo_daily_tb_win_arm64/). After some discussion on https://ask.libreoffice.org/t/windows-arm64-listing-in-downloads-page/102870, it was advised to contact this mailing list. We noticed that the lack of available machines for this platform could be a problem, and we discussed that with Microsoft, which could sponsors up to two (physical) machines for this. Let us know how we can help! Regards, Pierrick
