Open GoogleCodeExporter opened 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
Fixed with: http://hg.codeflow.org/pyglet/rev/8339eedde106
Original comment by pyalot@gmail.com
on 14 Aug 2009 at 4:11
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
Original comment by benjamin...@gmail.com
on 20 Aug 2009 at 2:04
@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
Original issue reported on code.google.com by
Bill.Jan...@gmail.com
on 20 Feb 2009 at 7:02