What do you mean by "link"? This term is more used in the C / C++ / native code world than in Java.
Basically, your jar will use whatever core.jar that the application will find in the classpath. Unless you use some API specific to 3.0+, it should be safe.
To compile the library we add core.jar to the class path, and I was wondering if by using core.jar 3.0a5 I was forcing users to also have that version.
Since I don't use any 3.0 stuff, I understand the version does not make a difference.
When I tried what? I don't have different OSes with different versions of Processing to try, so I thought I better ask to do the right thing. I think the docs don't mention which core.jar to use.
Comments
What do you mean by "link"? This term is more used in the C / C++ / native code world than in Java.
Basically, your jar will use whatever core.jar that the application will find in the classpath. Unless you use some API specific to 3.0+, it should be safe.
Ok, wrong term then :)
To compile the library we add core.jar to the class path, and I was wondering if by using core.jar 3.0a5 I was forcing users to also have that version.
Since I don't use any 3.0 stuff, I understand the version does not make a difference.
Thanks!
What happened when you tried?
When I tried what? I don't have different OSes with different versions of Processing to try, so I thought I better ask to do the right thing. I think the docs don't mention which core.jar to use.
So why don't you just download older versions of Processing and see what happens? You should probably be testing that anyway...