You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dependency org.lwjgl.lwjgl:lwjgl-platform:2.9.1 has native binaries for the respective OSs that Java needs to know about in order to run the project. We are currently leveraging the mavennatives plugin, however it can be more automated. The process of unzipping and setting the java.library.path variable needs to be relatively transparent to the developer.
Ideally you have it so only the OS you are building on gets those binaries unzipped. I have done this in the past, and with the help of the mavennatives plugin it is rather trivialcan be done, just not with the latest version of the plugin(0.0.7 as of 2014-11-12). It is just a matter of wiring it all up in a sane manner so that the build works in any environment.
The text was updated successfully, but these errors were encountered:
[edited to update link]
I had to fork the mavennatives plugin(git svn is fucking dope). The forked repo can be found here. I am in the process of getting my plugin into Maven Central. Once that is done our build will use a more updated plugin that I can update as needed.
I am also writing some code to append the directory for the natives to java.library.path. It currently feels really kludgy but I think with one or two more iterations I will have it picking up the OS via
System.getProperty("os.name")
and everything will be butta.
virtuoushub
pushed a commit
to virtuoushub/fuzzy-octo-shame
that referenced
this issue
Nov 19, 2014
The dependency org.lwjgl.lwjgl:lwjgl-platform:2.9.1 has native binaries for the respective OSs that Java needs to know about in order to run the project. We are currently leveraging the mavennatives plugin, however it can be more automated. The process of unzipping and setting the
java.library.path
variable needs to be relatively transparent to the developer.Ideally you have it so only the OS you are building on gets those binaries unzipped. I have done this in the past, and with the help of the mavennatives plugin it
is rather trivialcan be done, just not with the latest version of the plugin(0.0.7 as of 2014-11-12). It is just a matter of wiring it all up in a sane manner so that the build works in any environment.The text was updated successfully, but these errors were encountered: