From: Andy Polyakov Date: Fri, 15 Jul 2016 11:11:52 +0000 (+0200) Subject: INSTALL: clarify --cross-compile-prefix. X-Git-Tag: OpenSSL_1_1_0-pre6~217 X-Git-Url: https://git.openssl.org/?p=openssl.git;a=commitdiff_plain;h=85afea67f5e48dc4f02ac100454ec3caa41aa647 INSTALL: clarify --cross-compile-prefix. Reviewed-by: Richard Levitte --- diff --git a/INSTALL b/INSTALL index 0f246060fa..85a74b862f 100644 --- a/INSTALL +++ b/INSTALL @@ -85,10 +85,25 @@ --cross-compile-prefix=PREFIX The PREFIX to include in front of commands for your - toolchain. For example to build the mingw64 target on Linux - you might use "--cross-compile-prefix=x86_64-w64-mingw32-". - If the compiler is gcc, then this will attempt to run - x86_64-w64-mingw32-gcc when compiling. + toolchain. It's likely to have to end with dash, e.g. + a-b-c- would invoke GNU compiler as a-b-c-gcc, etc. + Unfortunately cross-compiling is too case-specific to + put together one-size-fits-all instructions. You might + have to pass more flags or set up environment variables + to actually make it work. Android and iOS cases are + discussed in corresponding Configurations/10-main.cf + sections. But there are cases when this option alone is + sufficient. For example to build the mingw64 target on + Linux "--cross-compile-prefix=x86_64-w64-mingw32-" + works. Naturally provided that mingw packages are + installed. Today Debian and Ubuntu users have option to + install a number of prepackaged cross-compilers along + with corresponding run-time and development packages for + "alien" hardware. To give another example + "--cross-compile-prefix=mipsel-linux-gnu-" suffices + in such case. Needless to mention that you have to + invoke ./Configure, not ./config, and pass your target + name explicitly. --debug Build OpenSSL with debugging symbols.