On 5/20/20 8:37 AM, Brian via lazarus wrote:
> On 5/20/20 5:50 AM, John Landmesser via lazarus wrote:
>> Am 20.05.20 um 01:12 schrieb Brian via lazarus:
>>>
>>> Regrettably, it appears I spoke too soon. I fired up Lazarus again and
>>> the problem is back. I'm compiling trunk for both fpc and
Alexey Tor. via lazarus schrieb am Mi., 27.
Mai 2020, 22:20:
> Win-aarch64 (arm64) is used in real hardware on Win10.
>
> installed FPC trunk with Laz trunk with Linux-x64->Win-ARM64 cross.
>
As long as the compiler can't compile itself on Windows on ARM64 I wouldn't
try anything as complicated
Win-aarch64 (arm64) is used in real hardware on Win10.
installed FPC trunk with Laz trunk with Linux-x64->Win-ARM64 cross.
on making CudaText with build mode "Win-arm64" I got strange errors:
..Compile package LCLBase 2.1, exit code 1
Error:
CudaText for Linux gtk2 x64.
its Python API fails when it reads current form, after plugin shows
InputQuery dialog.
I added test ShowMessage near the showing InputQuery and found that
after InputQ call, program reads empty Screen.ActiveForm.
marked by comment.
is it LCL bug?
LCL must restore