Hi Juan,
On Sat, Sep 28, 2013 at 8:40 PM, "Juan J. Martínez" <[email protected]> wrote:
> I didn't like fiddling with LD_* because some Linux distributions may
> not allow using them for security reasons (ie. Fedora with selinux
> enabled), restricting what ldconfig will do.
>
AFAIK, they restrict if LD_* used by ldconfig. But not how we use it
with ctypes (dlopen). So:
directories.extend(os.environ['LD_LIBRARY_PATH'].split(':'))
.. still work (that's at
https://code.google.com/p/pyglet/source/browse/pyglet/lib.py#268)
> If I had to support this, I would use a pyglet.options entry with a callable:
I would say we should support loading libraries from project directory
out of the box, i.e. without any configuration.
The complexity is to find out what "project directory" is. It may be
directory where sys.executable is, in case of running py2exe or
cx_freeze, or it may be a directory of the main script, or a workdir.
Maybe just search all of the above and their "lib", "lib/x86",
"lib/x64" subdirectories. Probably we could also use some py2exe or
cx_freeze hooks.
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/groups/opt_out.
