For fun, I tried manually stripping the GL libraries from Pyglet and adding the needed lines back in again by hand -- essentially, a brute-force implementation of what I was describing here. It didn't take long to add back in all the needed instructions to get my application running -- maybe ten minutes of manual labor. The end result was a savings of around 10-15MB in the application footprint when I launched it.
So, it seems like it would be worth doing, although again only as an advanced project for devs who want to squeeze max performance out of their Pyglet apps, and not as a default way to go. One other thing I'm thinking of is, rather than write a script, just provide my "stripped" copies of the GL libraries for those who want it, and allow people to swap them in if needed. That's the quick-and-dirty way to get people to try this out. -- 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 https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
