> Is it "difficult" to do?
It depends, but yes, in general I wouldn't shy from using the words "laborious" and "verbose" when it comes to wrapping native code. The process goes something along these lines:
[*]Create a new C or C++ project which would act as a "wrapper" … Read More
[quote]By this I imagine that you mean that nearly all the calculations in classes, functions, procedures, etc must be turned basically into usable functions in a C++ library right?[/quote]
Basically all classes and functions you create specifically for the purpose of JNI wrapping will go in this project. So you'll … Read More
OK, you should never have to add any random DLL to your path so for the time being forget about manually adding DLL's. How are you building the wrapper project: using IDE or command line? Using Visual Studio? How is your library distributed, as a DLL or LIB?
This is … Read More
I'm not sure what exactly are you doing there. After reaching home, it took me 30 mins to run the hello world example. Are you sure you are able to properly build the DLL file? The steps in the tutorial might be a bit problematic in case you are using … Read More
OK, you have to make sure that:
[*]javah is in your path (at least temporary; so that you can directly invoke it without being in java\bin)
[*]You need to be in a directory just outside the "mypkg" directory which contains your HelloWorld.class file before invoking javah. To do this, … Read More
> Could you be more especific when you say "setup the same thing in Visual studio"?
Simply set up a new DLL C project in Visual studio. Create new blank project. Right click project -> General -> Configuration Type set to Dynamic Library DLL
Right click Header folder -> add … Read More
> This might be a dumb question but would this make a normal C/C++ DLL or a C/C++ .NET DLL?
You would need a normal C/C++ DLL.
> And the C++ team pretty much have no clue how to make a .DLL
That's news. I hope you are not stuck … Read More
> C:\HelloWorld.dll: Can't find dependent libraries
When you load a DLL, the dependent DLL's get loaded as well and if they are not found, this error is raised. The dependent DLL's should be in the PATH env variable or in -Djava.library.path system property. Assuming you are not using -Djava.library.path, do … Read More