Mentioning [Python.Docs]: ctypes – A foreign function library for Python (although this doesn’t have very much to do with it) just in case. The underlying error is ERROR_BAD_EXE_FORMAT (193, 0xC1). Check it in [MS.Docs]: System Error Codes (0-499). It’s a general Win error (not related to Python). In the current case (related to Python), the … Read more
In order for System.loadLibrary() to work, the library (on Windows, a DLL) must be in a directory somewhere on your PATH or on a path listed in the java.library.path system property (so you can launch Java like java -Djava.library.path=/path/to/dir). Additionally, for loadLibrary(), you specify the base name of the library, without the .dll at the … Read more
LoadLibrary does not do what you think it does. It loads the DLL into the memory of the current process, but it does not magically import functions defined in it! This wouldn’t be possible, as function calls are resolved by the linker at compile time while LoadLibrary is called at runtime (remember that C++ is … Read more
From what I remember on Windows the search order for a dll is: Current Directory System folder, C:\windows\system32 or c:\windows\SysWOW64 (for 32-bit process on 64-bit box). Reading from the Path environment variable In addition I’d check the dependencies of the DLL, the dependency walker provided with Visual Studio can help you out here, it can … Read more
Members must be resolvable at compile time to be called directly from C#. Otherwise you must use reflection or dynamic objects. Reflection namespace ConsoleApplication1 { using System; using System.Reflection; class Program { static void Main(string[] args) { var DLL = Assembly.LoadFile(@”C:\visual studio 2012\Projects\ConsoleApplication1\ConsoleApplication1\DLL.dll”); foreach(Type type in DLL.GetExportedTypes()) { var c = Activator.CreateInstance(type); type.InvokeMember(“Output”, BindingFlags.InvokeMethod, null, … Read more
Contrary to the suggestions by some of the other answers, using the DllImport attribute is still the correct approach. I honestly don’t understand why you can’t do just like everyone else in the world and specify a relative path to your DLL. Yes, the path in which your application will be installed differs on different … Read more
This is a problem which can occur when there is an old version of a DLL still lingering somewhere around. Make sure that the latest assemblies are deployed and no duplicated older assemblies are hiding in certain folders. Your best bet would be to delete every built item and rebuild/redeploy the entire solution.
It looks like the perfect solution does not yet exist. To summarize some research: Make My Manifest (link) This tool scans a VB6 project to look for COM dependencies, but it also supports manual declaration of late-bound COM dependencies (i.e. those used via CreateObject). Interestingly enough, this tool puts all information about the dependencies inside … Read more
If you want plain C exports, use a C project not C++. C++ DLLs rely on name-mangling for all the C++isms (namespaces etc…). You can compile your code as C by going into your project settings under C/C++->Advanced, there is an option “Compile As” which corresponds to the compiler switches /TP and /TC. If you … Read more
Just package it anywhere in the jar. One thing you have to keep in mind though – before you can use the DLLs you need to actually extract these from the JAR and dump these on the hard disk somewhere otherwise you won’t be able to load these So basically – I did JNI project … Read more