Android Tutorial B4A on Parallels M1 MAC

B4A works fine in Parallels windows on M1 MAC.
Here are compilation times for same, fairly large project:
Could Erel comment on significant differences in time execution of various parts.
In particular:
M1 MAC: Building folders structure. (11.50s) Convert byte code - optimized dex. (25.41s)
PC: Building folders structure. (0.66s). Convert byte code - optimized dex. (3.54s)

Same project was opened from Synology Diskstation over network...

On Mac:
B4A Version: 10.70
Parsing code. (0.51s)
Java Version: 11
Building folders structure. (11.50s)
Compiling code. (10.83s)
Compiling layouts code. (3.30s)
Organizing libraries. (0.00s)
(AndroidX SDK)
Running custom action. (1.06s)
Compiling resources (1.80s)
Linking resources (5.27s)
Compiling debugger engine code. (2.10s)
Compiling generated Java code. (1.40s)
Convert byte code - optimized dex. (25.41s)
Copying libraries resources (2.55s)
ZipAlign file. (0.58s)
Signing package file (debug key). (1.92s)
Installing file to device.

On PC:
B4A Version: 10.70
Parsing code. (0.61s)
Java Version: 8
Building folders structure. (0.66s)
Compiling code. (3.27s)
Compiling layouts code. (0.19s)
Organizing libraries. (0.00s)
(AndroidX SDK)
Running custom action. (0.59s)
Compiling resources (6.16s)
Linking resources (3.48s)
Compiling debugger engine code. (8.05s)
Compiling generated Java code. (10.23s)
Convert byte code - optimized dex. (3.54s)
Copying libraries resources (1.74s)
ZipAlign file. (1.10s)
Signing package file (debug key). (3.26s)
Installing file to device. Error
No device found.

 

[Erel]

Test it with the project on the local disk. Running it over the network will make things much slower.

 

[Robert Zmrzli]

PC was also over network above...
M1 Macs are touted to be so fast but here is quite slower than my 5 years old PC.
Probably Rosetta and Arm windows add this overhead.

Anyway, I am happy that program runs fine.

On local disk:

First run:

B4A Version: 10.70
Parsing code. (0.74s)
Java Version: 11
Building folders structure. (0.12s)
Compiling code. (1.55s)
Compiling layouts code. (0.06s)
Organizing libraries. (0.00s)
(AndroidX SDK)
Running custom action. (5.99s)
Compiling resources (5.83s)
Linking resources (3.97s)
Compiling debugger engine code. (25.68s)
Compiling generated Java code. (20.02s)
Convert byte code - optimized dex. (21.08s)
Copying libraries resources (6.37s)
ZipAlign file. (1.59s)
Signing package file (debug key). (8.48s)

Second run: (without changing anything)
B4A Version: 10.70
Parsing code. (0.53s)
Java Version: 11
Building folders structure. (0.06s)
Compiling code. (0.96s)
Compiling layouts code. (0.02s)
Organizing libraries. (0.00s)
(AndroidX SDK)
Running custom action. (0.57s)
Compiling resources (0.08s)
Linking resources (1.07s)
Compiling debugger engine code. (0.05s)
Compiling generated Java code. (0.23s)
Convert byte code - optimized dex. (19.88s)
Copying libraries resources (2.12s)
ZipAlign file. (0.04s)
Signing package file (debug key). (1.27s)

Third run: (with small change )

B4A Version: 10.70
Parsing code. (0.50s)
Java Version: 11
Building folders structure. (0.04s)
Compiling code. (0.80s)
Compiling layouts code. (0.02s)
Organizing libraries. (0.00s)
(AndroidX SDK)
Running custom action. (0.62s)
Compiling resources (0.05s)
Linking resources (0.78s)
Compiling debugger engine code. (12.02s)
Compiling generated Java code. (0.05s)
Convert byte code - optimized dex. (19.45s)
Copying libraries resources (2.14s)
ZipAlign file. (0.04s)
Signing package file (debug key). (1.24s)

 

[ThorstenStueker]

@Robert: you could use also B4J on M1 or only B4a?
@Erel & @Robert: Does JDK 11 and JFX 11 work on Windows ARM?

I thought all the time JavaFX is not working in it's x86/64 Version on Parallels.