Win64 is also making good progress behind the scenes. The uncommitted Win64
UNO bridge I've been coding (a lot of it in AMD64 assembly) should now be
able to call arbitrary C++ methods from UNO and UNO methods from C++ (not
tested yet), but the poorly documented internals of MSVC C++ exception
han
Okay, have all special quick points to my OpenOffice overview[1]. (I
skipped the ODF, and Pivot part, since there are plenty Bugzilla Issues
which I will find at some point in the future ;P )
I think we have a lot of technical Debt, and Issues that needs to be
fixed. Not only in the building envir
+1 on doing what we can to move to gbuild as appropriate, but we also need
to find out what our long term plan is, esp as related to non-*Nix platforms.
I hope to get macOS more up-to-date and part of that is fixing the longstanding
confusion regarding UDK library versioning. Currently, AOO forces
Win64 is also making good progress behind the scenes. The uncommitted Win64
UNO bridge I've been coding (a lot of it in AMD64 assembly) should now be
able to call arbitrary C++ methods from UNO and UNO methods from C++ (not
tested yet), but the poorly documented internals of MSVC C++ exception
hand
Hi again;
I just wanted to stop by and share some ideas of things that need to be
done in AOO after 4.2.
Easier things:
OpenSSL has to be updated, yet again, and while the future versions will
be under an Apache License, making things nicer for us, the API has been
changing so we may need s
Hey guys!
Thank you to everyone getting involved in the new release. It is very
much needed and I was really tired of the continuous revamping of the
4.1 releases. It is now clear that we are also doing proper branching of
the releases.
Some of the issues off the top of my head that you may
Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
thinking...
76.372903 : lang : ##
76.372943 : lang : Registering extensions:
76.372991 : lang : ##
76.381173 : in
