On OS X in the terminal you can type: sysctl hw.machine
and it will display the machine architecture.
I don’t use the shell commands much but it looks like you
can get the info without compiling code by using the code
below.
on mouseUp
put shell( "sysctl hw.machine" ) into pData
put pData
On 2019-08-31 04:41, Devin Asay via use-livecode wrote:
No, I’m just toying with the idea of having a 32-bit launcher that
would examine the host OS, then launch the proper executable based on
whether it is 32 or 64 bit. Sort of like a poor man’s universal app
like we used to create for MacOS. It
Below is some c code that will return the architecture on
OS X.
/* Determine the machine name, e.g. "x86_64". */
#include
#include
#include
#include
int main(int argc, const char * argv[]) {
size_t size;
sysctlbyname("hw.machine", NULL, &size, NULL, 0); // Get size of data to
be r
On 8/30/19 8:41 PM, Devin Asay via use-livecode wrote:
No, I’m just toying with the idea of having a 32-bit launcher that would
examine the host OS, then launch the proper executable based on whether it is
32 or 64 bit. Sort of like a poor man’s universal app like we used to create
for MacOS.
On 8/30/19 8:41 PM, Tom Glod via use-livecode wrote:
on win32 i will run out of ram and lock up if not hard crash before
it even gets to it..and if i can test the standalone bitness I can
decline to attempt an impossible feat.
Ah. OK - so you're deploying a 32-bit application possi
I have personal experience with trying to create a graphic that is 32,000 x
32,000 and exporting it.
on win32 i will run out of ram and lock up if not hard crash before
it even gets to it..and if i can test the standalone bitness I can
decline to attempt an impossible feat.
on win64 i
On Aug 30, 2019, at 9:10 PM, Mark Wieder via use-livecode
wrote:
>
>> On 8/30/19 12:22 PM, Devin Asay via use-livecode wrote:
>>
>> Now that we can build both 32 and 64 bit applications for Windows, it’s
>> important to be able to tell whether the host OS is 32 or 64 bit.
>
> Why? If the 64-b
On 8/30/19 12:22 PM, Devin Asay via use-livecode wrote:
Now that we can build both 32 and 64 bit applications for Windows, it’s
important to be able to tell whether the host OS is 32 or 64 bit.
Why? If the 64-bit application won't run on the 32-bit system you won't
get as far as your scripte
Oh...
1. Yes, one way is to parse the exe. (offset, offset, check for "PE\0\0", next
two bytes)
2. Check for WoW64 redirection. (I'm not sure how, though.)
> On Aug 30, 2019, at 6:10 PM, Tom Glod via use-livecode
> wrote:
>
> I think he is asking to find out if the BUILD is 32 or 64 bit. In
I think he is asking to find out if the BUILD is 32 or 64 bit. In that
case the platform() function really has to be updated. but there is
porobably a way by reading the magic (file header) bytes of the
standalone. But can't be sure.
On Fri, Aug 30, 2019 at 5:43 PM Dar Scott Consulting via use-l
1. Check for files and folders that are are required on one or do not exist on
one.
Program Files (x86)
SysWOW64
2. systeminfo
> On Aug 30, 2019, at 1:22 PM, Devin Asay via use-livecode
> wrote:
>
> Hi all,
>
> I know we can get all manner of information about the host system our stack
Hi all,
I know we can get all manner of information about the host system our stack or
application is running on, including platform(), processor(), and machine() but
is there a way to check to see whether the host OS is 32 or 64 bit? The
platform function on Windows always returns Win32 regard
12 matches
Mail list logo
