On 20-jun-2006, at 19:08, Dan White wrote: > > On 15 Jun 2006, at 10:55, Ronald Oussoren wrote: > >> >> On 15-jun-2006, at 9:28, Dan White wrote: >> >> >>> >>> >>> So yes there are some DYLD_LIBRARY_PATH suff set. >>> >>> Maybe therein lies the problem...? >>> Python probably doesn't know about that stuff? >> >> That might be the problem, and seems to indicate that Intel does >> something completely wrong. Any use of the DYLD_* variables in a >> production environment is an indication that something fishy is >> going on. Unlike linux executables on osx contain the full path to >> libraries they link to. If DYLD_LIBRARY_PATH is needed the >> compiler doesn't include the full path to some libraries that are >> needed. It should be possible to teach py2app/macholib about this >> "feature" of the intel compiler, but you'll probably have to do >> that yourself. > > I tried fixing the .dylibs in my application bindle (made by py2app) > that were unable to find libguide.dylib > using for instance > > install_name_tool -change libguide.dylib @executable_path/../ > Frameworks/libguide.dylib /Users/dan/Desktop/bioimagexdsvn/trunk/ > dist/BioImageXD.app/Contents/MacOS/../Frameworks/ > libvtkGraphicsPythonD.5.1.dylib
Hmm, this could turn out to be interesting :-). Could you check the license of the intel compiler, are you allowed to do this? BTW. A better fix would be to rewrite the install_name of the libguide.dylib in /opt/intel/cc/.../, then py2app would automaticly copy the library and rewrite the install_name. Ronald _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
