Ronald Oussoren wrote: > My explanation seems to be bad, I meant to say sharing extensions across > different builds of the same Python version. One might install a normal > unix build in /opt/python and a framework build in /Library/Frameworks. Sorry, I didn't read your message carefully enough. This isn't a problem in Unix/ELF: you (normally) only put the name of the library into the resulting executable/library, not the absolute path. You then use the library search path (system-defined or LD_LIBRARY_PATH) to find the library. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4