Sat, 03 Jan 2015 20:18:00 +0100
Conditionally enable double key logic according to:
private browsing mode or privacy.thirdparty.isolate preference and
implement in GetCookieStringCommon and FindCookie where it counts...
With some reservations of how to convince FindCookie users to test
condition and pass a nullptr when disabling double key logic.
michael@0 | 1 | STLport for Android |
michael@0 | 2 | |
michael@0 | 3 | WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING |
michael@0 | 4 | WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING |
michael@0 | 5 | |
michael@0 | 6 | This feature is currently in beta. In case of issue |
michael@0 | 7 | please contact the android-ndk support forum or |
michael@0 | 8 | file bugs at http://b.android.com |
michael@0 | 9 | |
michael@0 | 10 | WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING |
michael@0 | 11 | WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING |
michael@0 | 12 | |
michael@0 | 13 | This directory contains a port of STLport for Android, which provides |
michael@0 | 14 | a simple STL implementation. Note that it currently does not support |
michael@0 | 15 | C++ exceptions and RTTI. Support for wchar_t and locales is probably buggy. |
michael@0 | 16 | |
michael@0 | 17 | You can either use it as a static or shared library. |
michael@0 | 18 | |
michael@0 | 19 | 1/ The static library is recommended if you will only produce |
michael@0 | 20 | one shared library for your project. All necessary STLport functions |
michael@0 | 21 | will be added to it. This option should also generate smaller |
michael@0 | 22 | overall binaries. |
michael@0 | 23 | |
michael@0 | 24 | 2/ The shared library, is recommended if you want to produce |
michael@0 | 25 | several shared libraries in your project, because it avoids copying the |
michael@0 | 26 | same STLport functions to each one of them, and having different instances |
michael@0 | 27 | of the same global variables (which can easily conflict or result in |
michael@0 | 28 | undefined behaviour). |
michael@0 | 29 | |
michael@0 | 30 | To use the *static* library, define APP_STL in your Application.mk as follows: |
michael@0 | 31 | |
michael@0 | 32 | APP_STL := stlport_static |
michael@0 | 33 | |
michael@0 | 34 | To use the *shared* library, use "stlport_shared" instead: |
michael@0 | 35 | |
michael@0 | 36 | APP_STL := stlport_shared |
michael@0 | 37 | |
michael@0 | 38 | Note that, in this case, you will need, in your application, to explicitely |
michael@0 | 39 | load the 'stlport_shared' library before any library that depends on it. |
michael@0 | 40 | For example: |
michael@0 | 41 | |
michael@0 | 42 | static { |
michael@0 | 43 | System.loadLibrary("stlport_shared"); |
michael@0 | 44 | System.loadLibrary("foo"); |
michael@0 | 45 | System.loadLibrary("bar"); |
michael@0 | 46 | } |
michael@0 | 47 | |
michael@0 | 48 | If both libfoo.so and libbar.so depend on STLport. |
michael@0 | 49 | |
michael@0 | 50 | You can build the STLport unit test program by doing the following: |
michael@0 | 51 | |
michael@0 | 52 | cd $NDK |
michael@0 | 53 | tests/run-tests.sh --test=test-stlport |
michael@0 | 54 | |
michael@0 | 55 | If you have an Android device connected to your machine, this will |
michael@0 | 56 | automatically try to run the generated test command. Note that for now |
michael@0 | 57 | a few tests are still failing (mostly related to wchar_t and locales). |
michael@0 | 58 | |
michael@0 | 59 | They should be fixed hopefully by a later release of this library. |
michael@0 | 60 | |
michael@0 | 61 | The NDK comes with prebuilt binaries for this library to speed up development. |
michael@0 | 62 | You can however rebuild them from sources in your own application build by |
michael@0 | 63 | defining STLPORT_FORCE_REBUILD to 'true' in your Application.mk as in: |
michael@0 | 64 | |
michael@0 | 65 | STLPORT_FORCE_REBUILD := true |
michael@0 | 66 | |
michael@0 | 67 | |
michael@0 | 68 | VERSION INFORMATION: This module is based on STLport version 5.2.0 |
michael@0 | 69 |