Thank you for the quick reply.
I only gave the virtual machine 6gb i've now increased it to 16gb (got 64gb on the mac).
I increased the timeout to 300s and it worked (took 105 secs), on a rerun it is 1.5s.
Thank you so much, it's currently slow, but at least it works.
I created a new app and compiled it , here are the timings for compilation on the first run, can you tell me if these are slow compared to a modern x86 machine ?
---------------------------------------------
Parsing code. (0.10s)
Java Version: 19
Building folders structure. (3.04s)
Running custom action. (0.17s)
Compiling code. (3.70s)
Compiling layouts code. (0.37s)
Organizing libraries. (0.04s)
(AndroidX SDK)
Compiling resources (0.38s)
Linking resources (0.78s)
build tools: 36.0.0, android jar: android-36
Compiling debugger engine code. (15.50s)
Compiling generated Java code. (16.42s)
Finding libraries that need to be dexed. (0.01s)
Dex: JavaObject (7.32s)
Dex code (92.35s)
Dex merge (9.53s)
Copying libraries resources (0.32s)
ZipAlign file. (0.14s)
Signing package file (debug key). (0.82s)
----------------------------------------------------
Will B4A run on Windows 7 ? (or even XP) instead of running a Virtualized Windows 11 (which then emulates x86 programs), i could emulate an Xp or Win7 system to try and speed things up if you think this is really slow.