Leaderboard

A guess :

The fix is on the way at least for a month. It's really shame that Embarcadero is silent on this issue. It's not a minor bug, but a major showstopper!

Here you go: Has anyone tried running Delphi on Windows ARM? - Delphi IDE and APIs - Delphi-PRAXiS [en] (delphipraxis.net) Can't blame you for not finding it, the forums search returns nothing on entering terms like "M1" or "ARM"

What is a hotfix: a small piece of code developed to correct a major software bug or fault and released as quickly as possible. This one probably will not be much hot...

We can now only hope that before Delphi 10.5 we will get at least one release of 10.4.2 without a major bug. From 10.4 to 10.4.2 every release had some issues :(. Embarcadero should change the release schedule. Now they are following the principle: "Ship it when the next major bug is checked in!".

I have solved it . Step 1 : create src\com\XLR folder in your App Directory there create the file BootReceiver.java with the following content : package com.XLR; import android.app.Activity; import android.content.BroadcastReceiver; import android.content.Intent; import android.content.Context; public class BootReceiver extends BroadcastReceiver { @Override public void onReceive(Context context, Intent intent) { Intent launchintent = new Intent(); launchintent.setClassName(context, "com.embarcadero.firemonkey.FMXNativeActivity"); launchintent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK); context.startActivity(launchintent); } } Step 2 : Under your App Directory create build.bat with following content : @echo off echo. echo Compiles your Java code into classes.dex echo Verified to work in Delphi 10.3.3 echo. echo Place this batch in a java folder below your project (project\java) echo Place the source in project\java\src\com\dannywind\delphi echo If your source file location or name is different, please modify it below. echo. setlocal set ANDROID_JAR="C:\Users\Public\Documents\Embarcadero\Studio\20.0\PlatformSDKs\android-sdk-windows\platforms\android-26\android.jar" set DX_LIB="C:\Users\Public\Documents\Embarcadero\Studio\20.0\PlatformSDKs\android-sdk-windows\build-tools\28.0.2\lib" set EMBO_DEX="D:\PRG\20.0\lib\android\debug\classes.dex" set PROJ_DIR=%CD% set VERBOSE=0 set JAVASDK="C:\Program Files (x86)\Java\jdk1.7.0_71\bin" set DX_BAT="C:\Users\Public\Documents\Embarcadero\Studio\20.0\PlatformSDKs\android-sdk-windows\build-tools\28.0.2\dx.bat" echo. echo Compiling the Java source files echo. pause mkdir output 2> nul mkdir output\classes 2> nul if x%VERBOSE% == x1 SET VERBOSE_FLAG=-verbose %JAVASDK%\javac %VERBOSE_FLAG% -Xlint:all -classpath %ANDROID_JAR% -d output\classes -source 1.6 -target 1.6 src\com\XLR\BootReceiver.java echo. echo Creating jar containing the new classes echo. pause mkdir output\jar 2> nul if x%VERBOSE% == x1 SET VERBOSE_FLAG=v %JAVASDK%\jar c%VERBOSE_FLAG%f output\jar\XLRBoot.jar -C output\classes com :Exit endlocal Step 3 : now run build.bat and it will create the class and jar files in the Output Directory in your App Directory. Step 4 : Alter your AndroidManifest.template like this <?xml version="1.0" encoding="utf-8"?> <!-- BEGIN_INCLUDE(manifest) --> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="%package%" android:versionCode="%versionCode%" android:versionName="%versionName%" android:installLocation="%installLocation%"> <uses-sdk android:minSdkVersion="%minSdkVersion%" android:targetSdkVersion="%targetSdkVersion%" /> <%uses-permission%> <uses-feature android:glEsVersion="0x00020000" android:required="True"/> <application android:persistent="%persistent%" android:restoreAnyVersion="%restoreAnyVersion%" android:label="%label%" android:debuggable="%debuggable%" android:largeHeap="%largeHeap%" android:icon="%icon%" android:theme="%theme%" android:hardwareAccelerated="%hardwareAccelerated%" android:resizeableActivity="false"> <%provider%> <%application-meta-data%> <%uses-libraries%> <%services%> <!-- Our activity is a subclass of the built-in NativeActivity framework class. This will take care of integrating with our NDK code. --> <activity android:name="com.embarcadero.firemonkey.FMXNativeActivity" android:label="%activityLabel%" android:configChanges="orientation|keyboard|keyboardHidden|screenSize" android:launchMode="singleTask"> <!-- Tell NativeActivity the name of our .so --> <meta-data android:name="android.app.lib_name" android:value="%libNameValue%" /> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity> <receiver android:name="com.embarcadero.firemonkey.notifications.FMXNotificationAlarm" /> <receiver android:name="com.XLR.BootReceiver" android:permission="android.permission.RECEIVE_BOOT_COMPLETED"> <intent-filter> <action android:name="android.intent.action.BOOT_COMPLETED" /> <category android:name="android.intent.category.DEFAULT" /> </intent-filter> </receiver> <!-- Registration is complete --> <%activity%> <%receivers%> </application> </manifest> <!-- END_INCLUDE(manifest) --> Step 5: Add the output\jar\XLRBoot.jar file to your Libraries inside Delphi and Run the programm. Step 6: After Run the Program Starts, Stop it Start it again . Now Reboot it will start. Turn Device Off and Turn On again and it will start. Thank you. SPECIAL NOTE FOR ANDROID 10 : You must set the Permissions System Alert window in Delphi. And on the Phone under App Info -> Advanced enable the Display over other apps settings.

All I am saying is that you don't need to special case INFs for comparison.

One thing to be aware of with EurekaLog is that it, in my experience, makes the link stage unbearable slow for large projects. This alone has made me replace it with madExcept in a few projects. I have my small grievances with madExcept too though. In particular the fact that it pumps the message queue, for no good reason, when processing silent exceptions.

UPDATE: I can confirm that Delphi 10.4.2 installs, builds and runs on a Mac M1 with a Parallels Desktop VM of WIndows 10 ARM (insider build). I successfully installed all my components (TMS, JVE, custom), build and ran both VCL (win32) and FMX (win32, MacOS64, Android32/64 and iOS64) perfectly. I'm going to keep using it for a while but if all goes well, this is a great solution and so much faster than my older Intel Macbook

IMHO Borland should've borrowed alias construction from SQL (select Foo as f, Bar as b ...) like this: with some.long.long.nested.object as foo do foo.bar := laz

Why should programmers care about building times? https://xkcd.com/303/