| Age | Commit message (Collapse) | Author |
|---|
|
I'm sure I'll live to regret this, but it does seem like our least worst
choice if we want to accurately represent the reality that different API
levels have different versions of zlib available.
Interestingly, today's archaeological dig turned up the fact that we
were wrong about when the 1.2.7.1 API appeared. It turns out that --
surprisingly -- 1.2.7 != 1.2.7.1 in terms of exposed API.
Note to self: move libz into the same apex as libc so we can get out of
this mess eventually, even if it takes another 10 years.
Bug: https://issuetracker.google.com/155351357
Bug: https://github.com/android/ndk/issues/1116
Test: builds
Change-Id: I77df497d89ce9e242458605fe5b08a3780c9d0f6
|
|
We can use zlib's own version script for this rather than maintaining
our own. I've copied theirs rather than modifying it in place to
avoid local changes to the zlib source and also to allow the
NDK-API-Council check in gerrit to check this file (it only checks
*.map.txt).
This removes a lot of decls that should have been private to zlib,
but it also correctly exposes decls that were added in in JB/JB-MR2,
whereas the old map claimed they were all added in L.
Test: make checkbuild
Bug: https://github.com/android-ndk/ndk/issues/230
Change-Id: Ib96b41e69d80a3bd28d3b85a0c96e70e6e73fb9d
|
|
Test: make checkbuild tests
Bug: http://b/30465923
Change-Id: Icdca01fa59f0f244f31c29146097bdebcb4d4eee
|
