I've now committed a preliminary Win64<->UNO bridge I've developed.
It compiles and links but haven't tested it yet.
On Thu, Dec 6, 2018 at 8:40 AM Damjan Jovanovic wrote:
> The main/bridges module has been ported to gbuild.
>
> It consists of 3 deliverables, java_uno.jar and its JNI code in a
The main/bridges module has been ported to gbuild.
It consists of 3 deliverables, java_uno.jar and its JNI code in a java_uno
C++ library which comprise the Java<->UNO bridge, and then an _cppu
library (eg. msci_cppu, gcc3_cppu) which comprises the C++<-> UNO bridge.
Blissfully, there are no heade
Thank you Patricia.
Yes knowing some x86_64 assembly would help, but don't go too far, it's
only about 2000 lines of code on other platforms. I don't know much of it
myself yet; just that the 32 bit registers grow to 64 bits and have an
additional name starting with "R" for the 64 bit version (eg.
I have many years of professional assembly language programming
experience. I have learned several assembly languages, but not one for
Win64. I also have a good general understanding of stack management and
call/return from compiler and operating system work.
Would it be useful for me to start
Good luck to you!
This is currently beyond my skill and time I can effort :(
I hope you keep going, Damjan!
On 01.12.18 09:22, Damjan Jovanovic wrote:
> Hi
>
> At least 81 modules (44.26%) successfully build on Win64 now, up from 67
> (36.61%) before.
>
> At present the build breaks in main/brid
Hi
At least 81 modules (44.26%) successfully build on Win64 now, up from 67
(36.61%) before.
At present the build breaks in main/bridges, which I can hack past, but
then modules like cli_ure and i18npool break, probably because they need
the missing Win64 UNO bridge.
This Win64 <-> UNO bridge ha
