Home/ Questions/Q 8174647
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T22:30:51+00:00

I am required to write a C++ application to run on an embedded Linux

  • 0

I am required to write a C++ application to run on an embedded Linux setup (DMP Vortex86DX processor). The vendor provides a minimal linux installation image that can be installed to the board and contains appropriate hardware drivers. My question is motivated by the answer to my previous question about writing Linux software on a particular kernel to run on a different kernel . I don’t really know where to start when it comes to writing the software with regards to ensuring compatibility.

My instinctive approach would be to install the same versions of g++ on the embedded device and on my desktop development machine, write the application on the dev maching, copy to the board and compile it there. This seems madness though and I find it hard to believe that this is how embedded software is developed. With regards to the answer to my previous question, is there a way I can simply build on my desktop but use the version of glibc that exists on the embedded device – if so how can enforce linkage to a specific version? Or is it possible to build everything statically so that the application doesn’t link to anything dynamically (I doubt this is possible).

I am a total novice to embedded development, and foresee months of frustration unless I can get hold of some good advice or resources. Any pointers or suggestion of where to start will be very gratefully received no matter how simple or trivial they seem – I really am starting at the very bottom with regards to embedded stuff.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    OK, given the fact that the Vortex86SX/DX/MX claims to be x86 compatible, a small set of compiler switches should enable you to compile code for your target machine: -m32 to ensure 32bit code, and no -march switch targeting a specific CPU.

    Then you’ll need to link your code. As long as you don’t use anything fancy, but simple established glibc functions, I’d expect the ABI to be the same on your development machine and the embedded system. In other words, you compile against your host libraries, copy the binary to the embedded system, and it should simply run using the libraries available there.

    If X-Linux were to use some other libc, like uclibc or similar, then you’d need a cross compiler on your host. I have little experience with Ubuntu in that regard, but I know that the sys-devel/crossdev package for Gentoo linux makes generation of cross-compilers very easy. This can be both for different architectures (not needed in your case) and different libraries (like e.g. uclibc).

    I’d say simply give copying the binaries a try, and report back if you encounter any problems there.

    • 0