Why are STM tools for Linux still 32-bit?

[Uwe Bonnes]

Most Linux distributions now are 64-bit. However the ST tools like

> file STM32CubeProgrammerLauncher

STM32CubeProgrammerLauncher: ELF 32-bit LSB executable, Intel 80386, version 1

are still 32-bit executables. Furthermore the programs are picky about the java version used. E.g. STM32CubeProgrammerLauncher needs openjfx. I can find openjfx for 64-bit, but not for 32-bit.

Please consider either providing both 32 and 64 bit variants, or switch to the 64-bit variant.

[Andreas Bolsch]

The "ELF 32-bit LSB executable" is a bit misleading here. It's statically linked, hence doesn't need any 32-bit library, and is in fact a simple wrapper for starting java (with the java classes hidden in this file). With "ps" you will see "java -jar STM32CubeProgrammerLauncher". Whether it uses 32-bit or 64-bit java and libs probably depends on the (java-) environment. At least on my system, it uses *ONLY* 64-bit libraries, as lsof shows.

With proper setting of environment variables, it's certainly possible to bypass this wrapper completely.

OpenJFX depency is a real nuisance, though, in particular if a distribution doesn't supply this package ... Had to build it myself.