On Tue, Jan 3, 2017 at 1:23 PM, Josua Mayer <[email protected]> wrote: > > > Am 03.01.2017 um 09:08 schrieb Roger Oberholtzer: >> On Mon, Jan 2, 2017 at 11:27 PM, Josua Mayer <[email protected]> wrote: >> >>> On the other hand, cross-compiling stuff on any distro that I am >>> familiar with has usually been easy. >>> The only case when I struggle is when there is a complex build-system >>> involved with hacked-together scripts not aware of cross-compiling. >>> There are many out there, but many others do just fine! >> On openSUSE, we use good old GNU make to build for openSUSE, Windows, >> as well as various TMS DSP, PPC, Intel MCS51 and ARM 920 based boards. >> I was just hoping to get the Raspberry into all this. Our makefiles >> work on openSUSE on the Raspberry. I was just hoping to get them to >> run on our build system as all the other do. >> > I'd say if you can cross-compile for mingw, you can cross-compile for > arm. There should be no difference in complexity. > The cross-compilers are even in the default repos now, i.e. > cross-armv7hl-gcc6.
The compiler is not the issue. It is the various libraries that an application may use. Unlike the windows libraries, which are placed off in some directory (the RPMs are so designed), the ARM ones are, of course, placed in the regular host location. So, for example, having the x86 libjpeg.so and ARM libjpeg.so files installed at the same time is not possible, unless you play with chroot or some other way to have the ARM things installed out of the way. I fear that it is too easy (for me at least) to make a mistake with this approach. It would be great if one could treat everything from a given repository in some way as a permanent setting. Like placing all aarch64 items in some tree other than /. And restricting these RPMs to only being able to write in that tree. -- Roger Oberholtzer -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
