To cross compile openSHH for ARM (in my case a mini2440) I did following: Install arm cross compiler – (eg. what is arm-linux-gcc and how to install this in ubuntu) Download: Zlib OpenSSL OpenSSH Build Zlib: cd zlib-1.2.7 CC=arm-linux-gnueabi-gcc ./configure –prefix=$HOME/zlibArm make make install Build OpenSSL: export cross=arm-linux-gnueabi- cd openssl-1.0.1c ./Configure dist –prefix=$HOME/opensslArm make CC=”${cross}gcc” … Read more
You would need to use the Windows Runtime C++ Template Library (WRL) directly, you wouldn’t be able to use C++/CX as Mingw doesn’t support it. Other than that, I think you just need the Windows 8 SDK, then you need to configure Mingw to use the headers and libraries. Also, you won’t be able to … Read more
Regarding your general questions: Why the C library works: The C library is part of your cross toolchain. That’s why the headers are found and the program correctly links and runs. This is also true for some other very basic system libraries like libm and libstdc++ (not in every case, depends on the toolchain configuration). … Read more
Try specifying the architecture/cpu. It sounds like the compiler is creating code with a higher architecture version than the emulator can handle. This might work: arm-linux-gnueabi-gcc -static -march=armv5 hi.c -o hi
Other answers, while technically correct, are more difficult than they need to be. There’s no need to use rustc (in fact it’s discouraged, just use cargo), you only need rustup, cargo and your distribution’s mingw-w64. Add the target (you can also change this for whatever target you’re cross compiling for): rustup target add x86_64-pc-windows-gnu You … Read more
As to build a version-less libcrypto, overwriting CALC_VERSIONS does the trick (at least for 1.0.2d): make CALC_VERSIONS=”SHLIB_COMPAT=; SHLIB_SOVER=” all Then, the sub-target link-shared of the target install_sw must be disabled (otherwise broken symlinks overwrite the libraries), which can be done by creating a dummy file of the same name at the suitable place (furthermore, SHLIB_EXT … Read more
If I use a cross compiler, how can I tell the value of the –host option I should give when I run ./configure? Three machines must be distinguished when discussing toolchain creation The build machine, where the toolchain is built. The host machine, where the toolchain will be executed. The target machine, where the binaries … Read more
You can use nm and size to get the size of functions and ELF sections. To get the size of the functions (and objects with static storage duration): $ nm –print-size –size-sort –radix=d tst.o The second column shows the size in decimal of function and objects. To get the size of the sections: $ size … Read more
CMake tries to compile an executable using “standard” (as per what CMake thinks is standard) compiler options and tries to run that executable, so to see if the compiler is working. The executable is simple like int main(int argc, char *argv[]) { return argc – 1; }. You can’t do that when cross-compiling. Because usually … Read more
You’re almost there. You’re adding your PATH to the SCons construction environment instead of to the ENV key of the construction environment: import os env_options = { “CC” : “nios2-linux-gnu-gcc”, “CXX” : “nios2-linux-gnu-g++”, “LD” : “nios2-linux-gnu-g++”, “AR” : “nios2-linux-gnu-ar”, “STRIP” : “nios2-linux-gnu-strip”, } env = Environment(**env_options) env.Append(ENV = {‘PATH’ : os.environ[‘PATH’]}) Export(‘env’)