Re: [glewpy-users] Linking of Mac build

[Joshua R. <jos...@us...>]

Hmm, you're right. Unfortunately, putting /opt/local/lib in my
DYLD_LIBRARY_PATH causes more problems than it solves. A symlink in
/usr/local/lib works though, so I think that's the solution I'll use for
now.

I suppose this is what I get for trying to mix manually-installed
packages with ones installed by DarwinPorts. :)

- Josh

Charles Moad wrote:
> I am assuming you are using the fat egg.  All the libraries built are
> dynamically linked.  When I compiled it I had glew installed in
> /usr/local/lib, but otool seems to list /usr/lib when it can't find the
> library.  Do you have your "LD_LIBRARY_PATH" variable set?  Set it to
> "/usr/local/lib" if that is where you installed glew.
> 
> - Charlie
> 
> Joshua Root wrote:
>> The Mac build seems to have the path to libGLEW hardcoded to /usr/lib.
>> Virtually no one will have it installed there; it will generally be in
>> /usr/local/lib, /sw/lib (for fink users) or /opt/local/lib (for
>> DarwinPorts users). I had to make a symlink in /usr/lib to get the
>> glewpy demo programs to run.
>>
>> Cheers,
>> Josh
>>