Yes, you’ll have to recompile the DLL for 64-bit. Your only other option is to switch to a 32-bit JVM, or otherwise get some 32-bit process to load the DLL on your behalf and communicate with that process somehow.
To run the functions in a DLL, first find out what those functions are using any PE (Portable Executable) analysis program (e.g. Dependency Walker). Then use RUNDLL32.EXE with this syntax: dllname is the path and name of your dll file, entrypoint is the function name, and optional arguments are the function arguments
These are API-sets – essentially, an extra level of call indirection introduced gradually since windows 7. Dependency walker development seemingly halted long before that, and it can’t handle API sets properly. So these are all false alarms and nothing to worry about. You’re not missing anything. Also see On API-MS-WIN-XXXXX.DLL, and Other Dependency Walker Glitches. … Read more
In my case it was the Explorer that was locking the DLL that was been compiled in the Debug folder… Strange, isn’t it? I found out using a tool called Unlocker. Had to delete with Unlocker, even when it was saying that there was no lock over the file, and I couldn’t delete the folder … Read more
Your commands are wrong ! Go to the directory where your main.cpp file is, and try the following. then you’ll no longer need to copy the DLLs (for your Hello World program). Other notes: The MinGW installation instructions recommends setting to the PATH environment variable. Normally the linker options should work (try all 3 of them at … Read more
This is almost certainly due to a missing dependency. Use a tool like Dependency Walker to find the required dependencies of the DLL. Or, if the DLL is supplied by a third party, read their documentation which should specify the required dependencies. Note that Microsoft.VC90.ATL indicates version 9 of MSVC which is VS2008. So you would need to install … Read more
Using PowerShell, you can execute this statement: The output will provide the Version, Culture and PublicKeyToken as shown below:
If all your code is indeed what is shown above, then I don’t see the problem. However, when I get this issue, sometimes its because malloc/new/whatever detects heap corruption, often this corruption has already occurred previously in the program, but the crash has been delayed until the next call to new/malloc. If you read other … Read more
At least for the ActiveState Python distribution, and in the official Python distribution: The dll is in where NN is the version number. On a 64-bit, a 32 bit dll will be installed here: and a running 32 bit application will magically translate this to the proper path, http://en.wikipedia.org/wiki/WoW64 When I link againsy Python27, I … Read more
Maybe another DLL necessary for MKL, such as libiomp5md.dll for example, is missing and causes the error. See Cannot load mkl_intel_thread.dll on python executable, my answer there and its comments. If this still does not solve your problem, try to manually copy other DLLs from the anaconda environment’s library path into the app installation directory and its lib subdirectory. Once … Read more