google-code-export / pyglet

Automatically exported from code.google.com/p/pyglet
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

suggest moving default location of AVbin library to pyglet.options #403

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Currently on darwin, the default location of the avbin dynamic library is
hard-coded as "/usr/local/lib".  For those of us installing Pyglet as part
of a larger system, it would be useful to be able to set that default
location.  In fact, I'd suggest that it would be useful to be able to do
that even on other platforms.  I'd like to suggest that pyglet.options
should have an option, "dynamic_library_locations", that should by default
be [], perhaps on Darwin ["/usr/local/lib",], and that the default
implementation of pyglet.lib.load_library should add any directories in
that option to the paths searched by LibraryLoader.load_library().

This would give a Python program using pyglet the option of setting this to
use a version of avbin in a non-standard location, without the overhead of
setting os.environ["LD_LIBRARY_PATH"], which is much heavier-weight because
it's passed on to subprocesses.

Original issue reported on code.google.com by Bill.Jan...@gmail.com on 20 Feb 2009 at 7:02

GoogleCodeExporter commented 9 years ago
(See also issue 398, in which this suggestion was originally raised.)

Original comment by ores...@gmail.com on 27 Jun 2009 at 7:07

GoogleCodeExporter commented 9 years ago
Fixed with: http://hg.codeflow.org/pyglet/rev/8339eedde106

Original comment by pyalot@gmail.com on 14 Aug 2009 at 4:11

GoogleCodeExporter commented 9 years ago
I can't see how this fix will implement this suggestion .  I still don't see 
any way
to specify a search path in pyglet.options.  Note that there are uses of Pyglet 
that
are not in apps, or even bundles, so adding a framework search option really 
doesn't
address this issue.

Original comment by Bill.Jan...@gmail.com on 14 Aug 2009 at 5:49

GoogleCodeExporter commented 9 years ago

Original comment by benjamin...@gmail.com on 20 Aug 2009 at 2:04

GoogleCodeExporter commented 9 years ago
@Bill.Janssen

Why don't you try if you can run whatever wasn't working now with that patch?

The search path specified for darwin is nothing but a suggestion taken into 
account
by pyglet among various other search paths. Pyglet wasn't finding avbin for 
whatever
reason, but ctypes did. It's my opinion that pyglet shouldn't fail when ctypes 
can do
the job. That's what this patch does, and that's what fixes your issue in not 
being
able to run avbin reliant code, regardless of what search path is specified for
darwin for avbin.

Original comment by pyalot@gmail.com on 20 Aug 2009 at 11:06