On Tue, 2010-03-09 at 07:45 -0600, mac9416 wrote:
> Hey, Giovanni,
>
> Thanks for the reply, that clears up a lot.
>
> Keryx (the app I'm working on) is a portable package manager for
> Debian-based systems, so it is only concerned with the OS's
> architecture.
>
> One fix we thought of is to read the output of 'apt-get -v' which
> provides architecture info. The only disadvantage is that the APT
> folks may change the output on us and throw Keryx off. That's why we
> hesitate to use that.
>
> Perhaps a more reliable alternative would be:
> """
> if struct.calcsize("P") == 4:
> os_arch = '32bit'
> elif struct.calcsize("P") == 8:
> os_arch = '64bit'
> """
>
> We're not sure how that works, but it it seems to, when run from
> source. Would this always return '32bit' if compiled on a 32-bit
> machine?
No, that wouldn't work as well, because it would return the equivalent
of sizeof(void*) for the Python being run, which would always be 32-bit.
"uname -a" provides architecture infos, and it is possibly more stable
than apt.
BTW, why can't you simply build keryx twice, one for 32-bit and one for
64-bit?
--
Giovanni Bajo
Develer S.r.l.
http://www.develer.com
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" 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/pyinstaller?hl=en.
