On 1/28/08, Drew Smathers <[EMAIL PROTECTED]> wrote: > I can't think of how pyglet.lib could be > patched to handle this case without making the so cache generation really > slow - like looking inside linker scripts to resolve the canonical path to > the so.
pyglet only creates its own so cache as a last resort (it was only added very recently, suggesting that not many people are needing it). Is it feasible to parse the script if loading the library fails? i.e.: 1. Try ctypes.find_library and default paths first 2. When these fail, generate so cache and look for hit 3. (new step) If hit doesn't load, assume it's a script and attempt to parse it. Or does this violate the linking rules? How complex do these scripts get? (I've only seen one or two, and the documentation suggests that they're used for many more linker activities than just redirection). Alex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
