nick woodward wrote:I'm getting the "unsatisfied link error"
I'd post code, but it isn't really important
Stevens Miller wrote:Nick, it's not enough to have the necessary libraries in proper directories. When you call a native method, it will fail unless the DLL containing that code has previously been loaded at run-time. Typically, you do that with something like this:
If a call like that is in the programs that work, but not in the one(s) that fail, simply copying the calls to the native methods from the working program to another program isn't enough. You have to load the native library with a call like one of the above, in that other program.
Campbell Ritchie wrote:No longer a “beginning” question. Moving.
nick woodward wrote:if I import a library it becomes 'native'
so you're saying that being native isn't enough, windows needs a reference to it too for every project?
is that what the classpath is?
I checked the properties of both projects to make sure that everything I could see was identical (even if I didn't fully understand it), and all the 'paths' it showed me were the same. Sorry, I'm a bit of a newb when it comes to this stuff.
-- having said that on the most recent restart netbeans is now complaining about a 'project problem', and the project itself has turned red (no exclamation mark). I can 'resolve' it automatically, but I'd rather improve my knowledge if you mind sparing a little more time or know of a dumbed-down link to follow!
Stevens Miller wrote:Good luck, Nick. The unloaded DLL actually is your problem, but everyone has to find their own way.
A timing clock, fuse wire, high explosives and a tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton