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 :-). If it's finished in time for the AOO42X release, then yes, we should. But it might have to be a beta release though. > > > > But there are still a lot of compiler warnings, and it sounds like LO > took > > years to get their Win64 version fully working. > > Always remember, the work on LO is mostly done by paid full time > developers. > > We are all volunteers who do it in our spare time... > And yet sometimes we get impressive stuff done despite so little manpower ;-). > > > > > A Win64 version is increasingly important, as Java is deprecating Win32 > > support. > > Yes, Win64 is important. > > But I don't see JAVA Win32 deprecated in the *near* future (at least not > for JAVA 8 and 11) > See https://openjdk.org/jeps/479 > > I only use the JAVA runtime from Adoptium, though. > > Regards, > > Matthias Regards Damjan
