Dear Endolf: I hope I don't sound annoying. I won't give any code a try that doesn't have a current tutorial attached to it. I can not afford to be hanging around for answers in forums. Also, as I said I'm really fluent with JOGL so cross platform API are already easy for me. Moreover, if I see JInput with proper documentation I might give it another try.
In answer to your email, yes, you will need to build each jar separately. Each platform jar has native components, we can't build OSX native .jnilib bits on windows etc. This isn't a JInput thing, this is an issue on any cross platform library that includes native components.
You'll also need to make sure the version of CGLIB on linux where you are compiling is the oldest version you want to support your deployed app, or modify the build to statically link, which is horrible, that's not a JInput thing, that's a compiling on linux thing.
Wintab is an API for tablet (as in artist, not small laptop) input, currently it's win32 only.
You should be running the top level ant file, it will work out what else needs running from the current platform.
From where you check JInput out too you should have a build.xml a readme text file, a couple of poms and some other files and the plugins directory, run ant at that level, not in the plugins. This will compile a JInput jar and a natives jar for the platform you are compiling on.
The target you probably want is dist, so run 'ant dist' in that directory.
Like I mentioned, you will need the platform SDK from MS and directx to build on windows, and on win32 you will need wintab too. There are environment variables that the build uses to know where those are
You will also need to run the vcvars batch file in the window you are running the compilation in to setup the VC variables.
For the love of Earth. I AM ABLE TO BUILD JINPUT! Yeesssss!!!
So if the Jars I get are the JIpunt.jar and the .dll s needed to run JInput on windows, it means I'm building JInput already right? Because my build gets stuck on the wintab folder, all the other things get built.
Moreover, what if I don't build the /wintab folder does that affect anything? What if I erase that /wintab folder part? Any pros and cons?
It really isn't that hard, if you can't compile JInput you'll struggle to create and implement a cross platform API to do exactly what JInput already does.
I agree with you. I don't encourage effort duplication and I succeeded in building JInput several times under GNU Linux. We have some efforts to do in order to integrate JInput in JogAmp and I really think creating another controller API from scratch would be a pure waste of time.