It seems that you are using the 64-bit version of the tool to install a 32-bit/x86 architecture application. Look for the 32-bit version of the tool here: and it should install your 32-bit application just fine.
The size of an int in Java is completely independent of the 32-bitness or 64-bitness of a JDK. It is always 4 bytes = 32 bits = −2,147,483,648 to 2,147,483,647. If you want a 64-bit integer, use a long, which is always 64 bits = 8 bytes.
Somehow, the Build checkbox in the Configuration Manager had been unchecked for my executable, so it was still running with the old Any CPU build. After I fixed that, Visual Studio complained that it couldn’t debug the assembly, but that was fixed with a restart.
I wish to import liblas module in Python 2.7 on window 64bit. If I import the module with IDLE (Python GUI) I have no problem. If I use PyScripter “PyScripter-v2.5.3-x64-Setup.exe” I get this error message. I have used liblas in PyScripter many times without problem and right now I can load all standard modules (e.g.: numpy, GDAL, etc.), but … Read more
It is a simple “file not found” kind of error, but with the very awkward behavior that it doesn’t tell you what DLL could not be found. Which might be the C++ DLL but also any implicit DLL dependencies it might have. Like the runtime support DLLs, very commonly missed, you can deploy them with … Read more
To start, I would suggest to test whether there is a problem between your application and its dependencies using dependency walker