On Thu, Feb 19, 2009 at 9:42 AM, Bill Janssen <bill.jans...@gmail.com>wrote:
>
> Yes, setting DYLD_LIBRARY_PATH for some specific purpose inevitably
> leads to confusion when some other program years from now expects a
> different setting.
I assume you are on a Mac, since you are using a dylib, and you have to take
into account that /usr/local/lib is a very common install directory (for
example: boost and mysql).
I would recommend just appending to your existing path, i.e.
export DYLD_LIBRARY_PATH=/usr/local/lib:$DYLD_LIBRARY_PATH
What I'd like to have is a pyglet.options setting
> which gives the default place to look for the library; that way I
> could override that in my Python program, perhaps after looking at my
> configuration file, and things would work.
This would be a fairly un-unix way of going about things, and would require
a fair amount of testing to get right - dlopen on the Mac is a strange
beast.
Or, have the option of installing the libavbin.dylib in the pyglet
> extension itself.
Have you tried just moving libavbin.dylib into /usr/lib?
sudo mv /usr/local/lib/libavbin.dylib /usr/lib/
I believe dlopen() should still be able to find it correctly.
However, I am not sure why you need to do any of this - the default install
location works fine on my Mac, without any modifications to paths.
--
Tristam MacDonald
http://swiftcoder.wordpress.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to pyglet-users@googlegroups.com
To unsubscribe from this group, send email to
pyglet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
