tag df9fe1f2efec3fddc4fc7276af0c179959ff3826
tagger The Android Open Source Project <initial-contribution@android.com> Tue Aug 14 13:22:32 2018 -0700
object fc8a786995b661f44da82cba00d23b3f5e92653c

Android N IOT Release 2 (NIT1.180611.010.B1)

commit fc8a786995b661f44da82cba00d23b3f5e92653c
author David Benjamin <davidben@google.com> Mon Jun 25 19:02:46 2018 -0400
committer David Benjamin <davidben@google.com> Mon Jun 25 19:07:17 2018 -0400
tree 9fb035fc76a693fc56aa0677659e3ecc8eda7894
parent c346395a614bdd8325f8375e83846a4d0f1cccb5

Use the same STL between lib{crypto,ssl} and tests.

BoringSSL is gradually adding some C++ APIs, so it and its tests need to
use the same STL.

This resolves a build error in an upcoming BoringSSL update. While I'm
here, fix the BORINGSSL_ANDROID_SYSTEM and BORINGSSL_IMPLEMENTATION
defines. The former should be on all targets, so we know not to test
things disabled on Android (though there aren't any currently), and the
latter should only be on libcrypto and libssl. (This only really matters
when building a shared library on Windows, but may as well get it
right.)

Test: mma
Change-Id: I7bd27d656e8cf4bf01119bd122bc71cd186921e2