Commit f73503c
committed
Fix linkage problems with python's versioned library (reintroduce
We fix this issue by re-introducing `INSTSONAME`. This variable has been used in all our python recipes, because allow us to remove the version of the compiled python library which is mandatory, at the time of writing, because android does not support versioned libraries (the Java method called to load the libraries only supports a .so suffix).
A little history, because I didn't find any official documentation for this variable, and **it's quite important for us**:
- This variable it's not hacked, it's official and was introduced a long time ago, forms part of the python's shared library building process (python/cpython@1142de3)
- @tito introduced this variable almost at the beginning of the p4a project in (bdefea1)
- @inclement also make use of it when he reworked the python2 recipe (4c8b5bc)
- this variable still exists in the current python2 recipe and we make use of it precisely to solve the mentioned android's libraries version problem
- Somehow, during the process of making the new python3 recipe, we loose this variable and then, we begin to have linkage problems at runtime with our python library as described in issue #1501
Note: ¡¡¡Special thanks to @Jonast!!!...to force me to search this information ;)
References: python/cpython@1142de3, bdefea1 and 4c8b5bc
Resolves: #1501INSTSONAME)1 parent 10351c2 commit f73503c
1 file changed
+8
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
231 | 231 | | |
232 | 232 | | |
233 | 233 | | |
234 | | - | |
| 234 | + | |
| 235 | + | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
| 239 | + | |
235 | 240 | | |
236 | 241 | | |
237 | 242 | | |
| |||
291 | 296 | | |
292 | 297 | | |
293 | 298 | | |
294 | | - | |
295 | | - | |
296 | | - | |
| 299 | + | |
| 300 | + | |
297 | 301 | | |
298 | 302 | | |
299 | 303 | | |
| |||
0 commit comments