LAMW - Compilation Error ("Cannot find system ..") lazarus / 43-Android ---------------------------------------------------------------------- BjPascal · 2018-07-17 10:13 using Lazarus 1.9.0  and FPC 3.1.1 on Win7 x64 Just installed Android stuff by using laztoapk, all went fine. Now I created my first LAMW project, and get this error: Cannot find system used by controls. Make sure all ppu files of a package are in its output directory. ppu in wrong directory=C:\fpcupdeluxe\fpc\units\arm-android\rtl\system.ppu.. Any idea how to fix it? I read older posting with the same problem, but they did not help. ---------------------------------------------------------------------- DonAlfredo · 2018-07-17 12:24 Use fpcupdeluxe (also) to install an arm-android cross-compiler ! ---------------------------------------------------------------------- BjPascal · 2018-07-17 13:31 Thanks DonAlfredo ! I already had done that, and redid it again. But the error remains. I checked and system.ppu is in the folder. Perhaps a wrong version of it? What else can I do? ---------------------------------------------------------------------- DonAlfredo · 2018-07-17 20:32 I will try to explain. Fpcupdeluxe installs a cross-compiler for ARMV7 and some more pre- defined settings, that work well for Android. LAMW has its own pre-defined settings. These settings can be seen in the project-options. There will see something with ARMV6 and softfloat. Just remove all these LAMW settings. If removed, your project will use the fpcupdeluxe settings and will find the correct system.ppu. Alternative: build cross-compiler with LAMW settings (ARMV6, softfloat). ---------------------------------------------------------------------- jmpessoa · 2018-07-17 21:29 if  you build your Lazarus/cross-arm using Fpcupdeluxe  then  select  "ARMV7a + VFPv3"  in  "new project"  settings... ---------------------------------------------------------------------- BjPascal · 2018-07-17 23:27 I now found the cause: In the past I had set the PathToAndroidSDK to a wrong folder. Since I did not know how to get back to this setting I found it in JNIAndroidProject.ini. After setting the proper path it now compiles and runs. I also selected  "ARMV7a + VFPv3" in the new project. Many thanks for your patience, you helped me a lot !! P.S. What SDK is currently wise to use? I installed API 22 ---------------------------------------------------------------------- jmpessoa · 2018-07-17 23:57 QuoteI installed API 22... Api 22 is good!  But, "AppCompat" [material] theme will need API >= 25 ---------------------------------------------------------------------- jmpessoa · 2018-07-18 19:42 Ok. Now the option  "ARMV7a + VFPv3" (*) link to: (*) Fpcupdeluxe ---------------------------------------------------------------------- pfms · 2019-01-28 19:58 Quote from: BjPascal on July 18, 2018, 01:27:29 amI now found the cause: In the past I had set the PathToAndroidSDK to a wrong folder. Since I did not know how to get back to this setting I found it in JNIAndroidProject.ini. After setting the proper path it now compiles and runs. I also selected  "ARMV7a + VFPv3" in the new project. Many thanks for your patience, you helped me a lot !! P.S. What SDK is currently wise to use? I installed API 22 I'm a similar problm, but after have checked my  JNIAndroidProject.ini file (correct in my case), I still have the same problem. Any additional suggestions? Is it possible to avoid FPCUPdelx, if it is possible. Thanks in advance ---------------------------------------------------------------------- jmpessoa · 2019-01-28 21:19 QuoteIs it possible to avoid FPCUPdelx, if it is possible... FPCUPdelux is a nice tool! But,  for windows you can try directly the package  laz4android + LAMW https://sourceforge.net/projects/laz4android/ side note: "LAMW 0.83"  changed "JNIAndroidProject.ini" to "LAMW.ini" ...