Re: Win64 port making progress

[Matthias Seidel]

Hi Damjan,

Am 05.01.25 um 18:14 schrieb Damjan Jovanovic:

On Sat, Jan 4, 2025 at 6:48 PM Damjan Jovanovic <dam...@apache.org> wrote:

On Fri, Jan 3, 2025 at 4:27 PM Damjan Jovanovic <dam...@apache.org> wrote:

On Fri, Jan 3, 2025 at 3:26 PM Matthias Seidel <
matthias.sei...@hamburg.de> wrote:

Hi Damjan,

Am 02.01.25 um 21:44 schrieb Damjan Jovanovic:

Hi

With my latest changes, 112 modules (60%) build successfully, and the
remaining blockers currently are:
- vcl, which is almost fixed. It needed changing SetClassLong() to
SetClassLongPtr(), and several other such Windows API changes for 64

bit

compatibility.
- connectivity, which builds but some of its DLLs (notably dbtools)

fail to

link, with mysterious missing symbol errors.
- testtools, which runs a UNO test, which fails as our Win64 UNO

bridge is

still buggy. But I am learning more about x86/amd64 assembly language,

and

Windows ABI details, such as C++ exception handling in assembly, and

hope

to fix that UNO bridge eventually.

That sounds great! Do you plan to cherry-pick that for AOO42X?

Thank you. With further fixes, 73.5% of modules build now :-).

It's going far better than expected. With further fixes, today we've
reached 158 out of 185 modules (85.4%) building successfully. I've also
updated the Wiki page (https://wiki.openoffice.org/wiki/Win64_port) with
various issues I've found during the port.

I've also done a preliminary port of the "connectivity" module to gbuild,
which successfully fixed its missing symbol issue. The same issue is now
affecting "chart2", so it might get ported to gbuild too ;-).

Today, after a preliminary gbuild port of "chart2", Windows/AMD64 building
reached the "postprocess" stage, the last stage before packaging. It breaks
there due to text file deficiencies (.xml, .srs, .xcu etc.) in my gbuild
ports of connectivity and chart2, which I hope to rectify soon, but the
fact we get that far means that all the code compiles and links, which is a
huge milestone.

I just tried a build but of course it stopped after some time.

Is this a private branch you work on or is it available via GitHub?

The next major challenge will be getting it to run. With an
incomplete/buggy UNO bridge, it will probably crash on startup.

I am eagerly waiting to test it when it fully builds!

Regards,

   Matthias

Regards
Damjan

smime.p7s
Description: Kryptografische S/MIME-Signatur