Skip to content

Commit 7f18efa

Browse files
authored
Updated README.md to clarify NDK versions (#1981)
* 📚 Updated README.dm to clarify NDK versions * 🔧 Change back to r19b
1 parent 57be583 commit 7f18efa

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

README.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -92,33 +92,33 @@ Please refer to the LICENSE file.
9292

9393
## History
9494

95-
In 2015 these tools were rewritten to provide a new, easier to use and
96-
extend interface. If you'd like to browse the old toolchain, its
95+
In 2015 these tools were rewritten to provide a new, easier-to-use and
96+
easier-to-extend interface. If you'd like to browse the old toolchain, its
9797
status is recorded for posterity at at
9898
https://github.com/kivy/python-for-android/tree/old_toolchain.
9999

100-
In the last quarter of 2018 the python recipes has been changed, the
101-
new recipe for python3 (3.7.1) has a new build system which has been
100+
In the last quarter of 2018 the python recipes were changed. The
101+
new recipe for python3 (3.7.1) had a new build system which was
102102
applied to the ancient python recipe, allowing us to bump the python2
103-
version number to 2.7.15. This change, unifies the build process for
104-
both python recipes, and probably solve some issues detected over the
105-
years. Also should be mentioned that this **unified python recipes**
106-
require to target to a **minimum api level of 21**,
107-
*Android 5.0 - Lollipop*, so in case the you need to build targeting an
108-
api level below 21, you must use an old version of python-for-android
109-
(<=0.7.1). All this work has been done using android ndk version r17c,
110-
and your build should success with that version...but be aware that the
111-
project is in constant development so, as per time of writing,
112-
``we recommend to use android's NDK r19b`` because the toolchains installed by
113-
default with the NDK may be used *in-place* and the python-for-android project
114-
has been adapted to that feature, so, it's mandatory to use, at least, ndk
115-
version r19 (be aware that more modern versions of the
116-
android's ndk may not work).
103+
version number to 2.7.15. This change unified the build process for
104+
both python recipes, and probably solved various issues detected over the
105+
years. It should also be mentioned that these **unified python recipes**
106+
require a **minimum target api level of 21**,
107+
*Android 5.0 - Lollipop*, so in the case that you need to build targeting an
108+
api level below 21, you should use an older version of python-for-android
109+
(<=0.7.1).
110+
111+
Be aware that this project is in constant development so, as per time of writing,
112+
you should use a minimum on Android's NDK r19, and ``we recommend using NDK r19b``.
113+
This is because the toolchains installed by
114+
default with the NDK can be used *in-place* and the python-for-android project
115+
has been adapted for that feature. Also be aware that more recent versions of the
116+
Android's NDK may not work.
117117

118118
Those mentioned changes has been done this way to make easier the transition
119119
between python3 and python2. We will slowly phase out python2 support
120120
towards 2020...so...if you are using python2 in your projects you should
121-
consider to migrate it into python3.
121+
consider migrating it into python3.
122122

123123
## Contributors
124124

0 commit comments

Comments
 (0)