Yeah, even an old raspberry pi should work, or just run a minimal system in qemu.
If you succeed there, you can then play around with cross-compiling.
BTW, what error (about the incompatibility) you get from the linker?
AlexandreHURDYK
@AlexandreHURDYK
It just says "skipping incompatible ../ext/oatpp-1.3.0/lib/cortexa9hf_neon_Release/liboatpp.a when searching for -l:liboatpp.a" as an information message
And then we get "collect2: error: ld returned 1 exit status" probably because the linker couldn't find the skipped libraries.
So, if you have access to an old raspberry pi, that would be the easiest way to build it for your target (armhf) architecture.
Another option is to use qemu virtualisation.
AlexandreHURDYK
@AlexandreHURDYK
I don't think we have something like that, but maybe we can use the piece of hardware we're using that hosts our homemade OS in the same way. I'll try to ask a coworker. If all else fails, it's qemu time to emulate a raspberry PI, right ?
It's literaly a circuit board with an home made OS inside. Jobplace gave this to me monday without much precisions and told me to make my program work on that circuit board.
So I'm afraid that I lack a lot of critical information about what that improvised computer can do.
:/
I can however try to ask a coworker in a few minutes.
Okay, but then that's maybe not a question for this forum. If you are going to cross-compile for an embedded device, that's quite a specialised discipline... I can try to compile oat++ on my lime2 this afternoon (which is 32 bit arm), but that one runs a full debian distro.
AlexandreHURDYK
@AlexandreHURDYK
All I should need is the two static library files so maybe just doing that on that debian distribution could work.