Hello everyone, I would like to ask the difference between the 32-bit and 64 bit versions of “Windows exe” released by “OpenFL”? Thank you
The Windows exe released by OpenFL,
32-bit and 64 bit,
What’s the difference?
Is there anything different?
64-bit executable support the ability to use more memory. In some cases, 64-bit executables can have faster performance.
32-bit Windows cannot run 64-bit executables. However, 64-bit Windows can run 32-bit executables. If you want maximum compatibility, you might prefer to build 32-bit executables.
That being said, the latest version of Windows doesn’t even have a 32-bit edition anymore. 64-bit Windows has been the default for a while now. With that in mind, with a 32-bit executable you’d be supporting a very, very small number of users that haven’t upgraded, and they will probably upgrade very soon.
I’d recommend 64-bit.
Okay, I understand. Thank you very much for your reply.
Hello, may I ask what is the difference between the Windows exe released by OpenFL and the Windows exe released by Adobe Air SDK? Is there anything different? Thank you
The typical windows .exe from OpenFL runs the haxe code transpiled to c++
In my tests with the lib I’m about to release, OpenFL windows .exe has better performance than AIR
1 Like
The AIR SDK bundle / executable is more comparable to Haxe’s Neko or HashLink, in that all of these are designed to run applications within a virtual machine. Running within a virtual machine typically comes at a performance cost.
AIR’s virtual machine is ActionScript VirtualMachine 2 (AVM2) (doc), and this is used on all of AIR’s supported platforms, except iOS I believe.
As @Matse noted, OpenFL is able to produce a native C++ application, which does not use a virtual machine and in many instances, offer significant performance benefits.
I’m glad to see your reply, thank you.