Porting a Delphi 13 Console Application

Elements Oxygene
1

Hi, I’m new to Oxygene / Water. I’ve downloaded the trial with the aim of getting my Delphi chess engine (Juggernaut) working with Oxygene. It’s a console application (UCI chess protocol) so I would have thought it would be easy. My aim is to see if Oxygene produces fast, support other platforms (Linux and MacOS), a utilize some of the vector capabilities for NNUE position evaluation.

When I initially tried to compile, I was asked to install Delphi 13 compatibility. This took a while and there were the following errors:

E: Error processing Winapi.EdgeUtils (rtl): Next Address (317) is already taken (<DelphiLocalDeclRecord 316’Result’>).
E: Error processing Winapi.EdgeUtils (rtl): Next Address (363) is already taken (<DelphiLocalDeclRecord 362’Result’>).
E: Error processing FMX.WebBrowser.Win (fmx): RefAddrDef invalid reference 2947, Addresses.Count=2943
E: Error processing FMX.WebBrowser.Win (fmx): RefAddrDef invalid reference 2523, Addresses.Count=2519
E: Error processing Vcl.Edge (vcledge): RefAddrDef invalid reference 3332, Addresses.Count=3328
E: Error processing Vcl.Edge (vcledge): RefAddrDef invalid reference 3052, Addresses.Count=3048

When I tried to compile Juggernaut I got the following errors:

W: Delphi support folder for Delphi 13 was not found at ‘C:\Users\steve\AppData\Local\RemObjects Software\EBuild\Delphi Support\Delphi 13’.
E: Reference ‘Island.DelphiSupport’ could not be resolved for target ‘Windows’ (Island Windows x86_64).

How can I fix this?

Thanks,

Steve

2

Anyone there?

3

Hi Steve - my apologies - I’ve raised this on our internal chat. We’re discussing.

4

Hi Steve,

My apologies for the late reply. The import errors you quoted are somewhat expected right now; just this one unit contains some data in the dcu format that we cannot handle properly yet, but it should just skip that unit and move on. That said, IslandDelphiSupport will normally be built at the end of the import process; if you see an error that it can’t be found, that means it probably was not, and maybe something else failed that I can’t glean from the log snippet.

Can I ask you to enable the highest level of logging in Tools/Options (“Diagnistic”, I believe), re-run the import, and post the complete log, so we can have a look what really failed to stop the import from building IDS?

Thanx,
marc

5

Hi — thanks for the reply. I’ve just seen it. I’ll do as requested and post result,

-– Steve