New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve deployment of native libraries #8
Comments
The main tasks should be done:
... The last point was, once more, a hassle, and it might not yet be the final solution. Details will be discussed in the forum. |
Sorry for the "ping", but ... I'd really appreciate feedback by @MysterionRise in view of these changes in relation to mavenized-jcuda (which (sorry!) is supposed to be made obsolete by these changes as soon as possible) |
Will do my friend, should have some time tomorrow On Sep 11, 2016 22:46, "Marco Hutter" notifications@github.com wrote:
|
The basic infrastructure is there and seems to work. Details about the POMs and the further path for bringing JCuda into Maven Central are discussed in #14 |
(EDIT: This was supposed to be opened by jcuda - sorry, I was logged in with the wrong account)
This is a very broad issue, but it can hardly be broken down into individual steps
The current deployment of the native libraries has to be improved. Right now, the natives are deployed as real native libraries (
.SO
,.DLL
and.DYLIB
files). These are built with CMake, and declared as own artifacts with Maven, in their own POM. (See https://github.com/jcuda/jcuda/tree/master/JCudaDriverJNI for an example). The deployment could be simplified (and be more in line with the Maven philosophy) if the natives could be packed into JAR files, and unpacked and loaded at runtime. There are several (intedependent) tasks on the way to this goal:LibUtils
classes have diverged. One step would be to update the LibUtils of JCuda so that it might eventually converge with the JOCL LibUtils (and maybe even become a standalone library in the future)JCudaDriver-windows-86_64.dll
, and thus, it would not be possible to have different versions of them on the same system. This could be solved by adding a version string, so that the library is named, for example,JCudaDriver-0.7.5c-windows-86_64.dll
JCudaDriver-0.7.5c-windows-86_64.jar
I also opened a new thread in the forum for discussing the details, options, and the usual Maven loops that one has to jump through.
The text was updated successfully, but these errors were encountered: