On Wednesday, October 29, 2003, at 01:40 PM, Jack Jansen wrote: > > On 29-okt-03, at 21:13, Keith Jackson wrote: > >> Is there a problem with using the "--bundle_loader" option to the >> linker to solve this problem when I don't have an easy way to modify >> the C code? If I understand correctly, I could modify the setup.py to >> add the bundle loader option, and then the bundle would be able to >> link to the _environ in the python inerpreter. > > Sounds like it could work. Let us know, > It works fine for building 4Suite. It also works for building a bunch of my own code. I tried it on a couple of modules that built fine without it, and they still work. Should this be in the LDSHARED variable in the python Makefile. That way all bundles would be built with the -bundle_loader option? This seems a lot easier then having all extension module writers ifdef their code to use environ. --keith
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