diff options
author | Andy Polyakov <appro@openssl.org> | 2018-08-06 09:43:39 +0200 |
---|---|---|
committer | Andy Polyakov <appro@openssl.org> | 2018-08-07 08:53:12 +0200 |
commit | f44d7e8b472dfc0602f8d06ef72e808a5e8d410c (patch) | |
tree | f19a31523638b6bf9d2b98f19f27de00376895fe | |
parent | 38eca7fed09a57c1b7a05d651af2c667b3e87719 (diff) | |
download | openssl-f44d7e8b472dfc0602f8d06ef72e808a5e8d410c.tar.gz |
INSTALL,NOTES.ANDROID: minor updates.
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/6866)
-rw-r--r-- | INSTALL | 10 | ||||
-rw-r--r-- | NOTES.ANDROID | 4 |
2 files changed, 8 insertions, 6 deletions
@@ -145,8 +145,8 @@ 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 + discussed in corresponding Configurations/15-*.conf + files. 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 @@ -157,10 +157,12 @@ "--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. + name explicitly. Also, note that --openssldir refers + to target's file system, not one you are building on. --debug - Build OpenSSL with debugging symbols. + Build OpenSSL with debugging symbols and zero optimization + level. --libdir=DIR The name of the directory under the top of the installation diff --git a/NOTES.ANDROID b/NOTES.ANDROID index 103ed87f3e..d13f47d667 100644 --- a/NOTES.ANDROID +++ b/NOTES.ANDROID @@ -46,8 +46,8 @@ One can engage clang by adjusting PATH to cover NDK's clang. Just keep in mind that if you miss it, Configure will try to use gcc... Also, PATH would need even further adjustment to cover unprefixed, yet - target-specific, ar and ranlib (or not, if you use binutils-multiarch - on your Linux). + target-specific, ar and ranlib. It's possible that you don't need to + bother, if binutils-multiarch is installed on your Linux system. Running tests (on Linux) ------------------------ |