On Mon, 2011-11-28 at 15:01 +0100, Martin Zibricky wrote:
> Giovanni Bajo píše v Po 28. 11. 2011 v 01:37 +0100:
> > Hi Matysek,
> > 
> > I'm trying to sort out the work that it's being done on the Mac side,
> > on
> > @executable_path.
> > 
> > It looks like your recent work has basically reverted this commit:
> > http://www.pyinstaller.org/ticket/46
> > 
> > Is that correct?
> 
> In general, yes. The approach with 'DYLD_LIBRARY_PATH' is wrong and
> causes more trouble.
> 
> There is one issue with using @executable_path. It seems to me that it
> is exposing a bug in pyinstaller.
> 
> http://www.pyinstaller.org/ticket/451

It doesn't sound any ring to me...

> > If so, why did you go with the largish Macho lib instead of simply
> > spawning install_name_tool?
> 
> Because with macholib we do not depend on having XCode installed on Mac.
> (tools - otool, install_name_tool). And that was my original motivation
> for looking at macholib.
> 
> http://www.pyinstaller.org/ticket/365
> 
> Now we use macholib for several things:
> - decide if a dll is a system library or not
> - resolve dll dependencies
> - find absolute path to a dll
> - set relative paths (@executable_path)
> 

Makes sense, thanks!
-- 
Giovanni Bajo   ::  [email protected]
Develer S.r.l.  ::  http://www.develer.com

My Blog: http://giovanni.bajo.it

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to