On Thu, Dec 22, 2016 at 4:49 PM, Hector Oron
Hello,
2016-12-22 10:40 GMT+01:00 Roger Oberholtzer
: I also install from OBS the various libraries needed for the Windows cross compile. They are nicely put in /usr/i686-w64-mingw32/sys-root/mingw or /usr/x86_64-w64-mingw32/sys-root/mingw. They are not installed in the Linux /usr/bin/ or /usr/lib/ trees.
Would it matter if host tools install in host paths? I think it would be fine to also be installer in /usr/bin, /usr/lib.
I just need to make sure that /usr/bin/gcc and all are not replaced so they run the ARM version. In my makefiles, when doing a cross compile for Windows, I define the tools. gcc is, for example, /usr/bin/i686-w64-mingw32-gcc or /usr/bin/x86_64-w64-mingw32-gcc. These cross-compilers do not replace /usr/bin/gcc,
Unfortunately, I am guessing this would not be the case for ARM packages (e.g., libjpeg8-8.1.2-40.2.aarch64 and libjpeg8-devel-8.1.2-40.2.aarch64). They would be installed in the /usr/bin/ or /usr/lib/ trees, as that's where they are expected to be. Which is perhaps not what I want on a cross-compiling system
Install in a sysroot (directory for cross building purpose)? https://gcc.gnu.org/onlinedocs/gcc/Directory-Options.html
Those are the compiler and such options. That is no problem. My concern is when zypper/rpm install ARM stuff that it will put it in /usr, and replace the files for the host system. This is not good. I need the host files for 'normal' functioning and compiling, and the ARM ones off somewhere for cross-compiling. Exactly as is dons for the Windows things created in OBS. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org