armhf | interesting stuff about arm devices

The error message is pretty clear

Cannot Find FFMPEG

You can install it via sudo apt install ffmpeg libavcodec-dev libavformat-dev libavfilter-dev

1 . Erase the sdcard you are using (if it is not carrying some data you don't want to lose) 2. Download a previous version of pios or upgrade the current one

Install like this:

Not sure why, but I can see the menus and variables. Even removed the linux folder made a clean start.

Here the commands ran:

A command similar to this one lists all the predefined macros of your compiler (of course, you have to replace g++ by your actual compiler for the specific target, and add the specific options for this target).

Sorry, I was making some mistakes in configureing bcm2711_defconfig file. Thanks for everyone for trying to help me:)

I realized that if I removed the target definitions altogether and let the arm64 docker environment build the rust app it works as expected. Thanks to @user1937198, I found that using "aarch64-unknown-linux-musl" as the target allowed the static build of the arm rust in the container. The working docker file is below

Unfortunately, the C++ stream-based I/O library is generally underused since everybody "knows" that it performs poorly, so there's a chicken and egg problem there - bad opinion leads to little use leads to sparse bug reports leads to low pressure for a fix.

I'd say that the largest user of C++'s streams is the basic CS/IT education sector and "quick one-off scripts" (that will invariably outlive the author), and there nobody really cares about performance.

What you're seeing is just a wasteful implementation - it constantly allocates and deallocates somewhere in the guts, but it doesn't leak memory as far as I can tell. I don't think that there's any sort of a "pattern" that will guarantee better performance in a non-brittle way while using stream I/O.

The best strategy to win at this in an embedded setting is not to play the game at all. Forget about the C++ stream I/O and all'll be good. There are alternative formatted I/O libraries that bring back the C++'s type safety and perform much better and then you're not beholden to standard library implementation bugs/inefficiencies. Or just use sscanf if you don't want to add dependencies.

The correct way to deal with this for most things that use JavaCPP is to set the javacpp.platform property.

When building with mvn -Djavacpp.platform=linux-x86_64 you will get only that specific platform and nothing else. This will also apply to all other transitive dependencies, e.g. opencv.

You can try running mvn -Djavacpp.platform=linux-x86_64 dependency:tree to see that it works.