Hi Juan, On Sat, Sep 28, 2013 at 9:23 PM, "Juan J. Martínez" <[email protected]> wrote: > On 28/09/13 19:19, "Juan J. Martínez" wrote: >> [...] >>> >>>> I like searching in current >>>> script dir and lib directories (lib/x86 and lib/x64 doesn't make sense >>>> because... ARM etc hehe). >>>> >>> >>> How about "lib/" + platform.machine() ? >>> >> >> Fair enough. I can do that! > > Eh, not really... I get i686 here and that's not what we are looking for :D >
I wouldn't care if the would be called i686/x86_64. However there are rumors that it seems to be non-reliable on OS X. > See what I was doing for the "bits" in my original code: > > bits = "64bit" if sys.maxsize > 2**32 else "32bit" > > ...but it is because I was assuming Intel/AMD only. I think we may have > to go with the "lib" version only. After all it doesn't make sense to > distribute a single package for Linux, Mac, Windows x n-architectures. > Mac usually uses universal binaries. For Windows I doubt I will build 64bit version soon, because that needs VS license. So only system affected is linux, outlined in your use case. I don't distribute pyglet apps for Linux (yet), so I don't care much. (For development system avbin is just OK). -- Paul -- 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.
