binutils path / ndk23b problem

[grl]

HI!

Trying to get LAMW on linux up and running on a fresh Linux mint installation.

Using fpcupdeluxe I got fpc and lazarus stable and built the crosscompilers.
Got android studio and used the sdk manager to get sdk and ndk (23.1.7779620, no version selectable, that is what you get)

Then I configured the LAMW-paths in the Lazarus GUI:

Code: [Select]

JDK: [homedir]/Android/android-studio/jre
ANT: predefined by fpcupdeluxe to [homedir]/LazAndroid/ccr/lamw-ant/apache-ant-1.10.12/bin
Gradle: predefined by fpcupdeluxe to [homedir]/LazAndroid/ccr/lamw-gradle/gradle-7.3.1
NDK: [homedir]/Andoid/Sdk/ndk/23.1.7779620
SDK: [homedir]/Android/Sdk

Then tried to compile a simple LAMW GUI project.
This stops after a while with the message

Code: [Select]

unit1.pas(31,0) Error: Assembler arm-linux-androideabi-as not found, switching to external assemblingEnabling the logging in Lazarus showed that it searches for it in

Code: [Select]

[homedir]/Android/Sdk/ndk/23.1.7779620/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_32/bin/arm-linux-androideabi-asbut this path is not existant in ndk23. Not sure if this is by design and google changed some path there....

The only traces of a suitable as in this ndk version is in

Code: [Select]

Sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/arm-linux-androideabi/binThere is a smylink called as but it points to some /buildbot/src/android.... path and that I don't have....

So perhaps could someone with a bit more Android / ndk knowledge take a look at that?

Then I got ndk22b directly from the google page - wanted to know if this might be an ndk problem.
There everything worked as expected, as found in the expected path, build process finished successfully.

The only little problem was, that it took me some time to realize that I couldn't find a way to change the ndk-path in an existing project. Its always using the ndk-path set at "create project" time. If I change the ndk path in the LAMW-options later on it still uses the old path (and using the non-working ndk23b in my case).

So my second question: is this intended? Or was I just too stupid to find how to change the ndk-path?



Thanks
Lukas

[DonAlfredo]

My guess.
The latest NDK's are pure LLVM based. So, the "normal" linker and/or assembler are not available anymore.
That is why an older NDK still (and will) work.