diff options
author | Jan Mulder <jlmulder@xs4all.nl> | 2019-07-11 19:16:13 +0200 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2019-07-18 06:39:00 -0700 |
commit | 9a70c260e8b7f600c567fe4f09d759f6abe54d02 (patch) | |
tree | fc29ad88d80a9b17639129792ce0ec809f4e9d8a /packaging/android/android-build-wrapper.sh | |
parent | bb895f18962c3f30e5d034861a73d22e6460743e (diff) | |
download | subsurface-9a70c260e8b7f600c567fe4f09d759f6abe54d02.tar.gz |
Android: rework build of OpenSSL to get it to build link and run
This is squashed commit consisting of a number of subjects, all intended
to get our app to build, link and run on device, but as the steps are
small (but non-trivial), I document them in this one commit.
1) Do not use OpenSSLs install targets, but simply copy the wanted build
artifacts manually. The main reason for this, is that the install
targets want to install a lot more than we build, so it also builds
parts of the OpenSSL suite that we will never use.
2) As Android does not like shared libraries with embedded versioning
(and the used androiddeployqt actively prevents adding versioned
libraries to the build), strip all this data from the generated shared
libraries. This trick was already there, but its adapted to all possible
conflicts.
3) The OpenSSL config script seems rather broken, resulted in failed
builds, and calling the underlying Configure is simpler.
4) Finally, parts of the OpenSSL code uses stdio things like stdout,
stderr, etc. These showed up as undeclared external on build time. Well,
luckily, there was an easy way out using 2 -D(efines). This feels hacky,
but does the job (and we are not interested in the output of OpenSSL in
our app).
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
Diffstat (limited to 'packaging/android/android-build-wrapper.sh')
0 files changed, 0 insertions, 0 deletions