Skip to content
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

Have build system handle native binaries more elegantly. #11

Open
virtuoushub opened this issue Nov 4, 2014 · 2 comments
Open

Have build system handle native binaries more elegantly. #11

virtuoushub opened this issue Nov 4, 2014 · 2 comments

Comments

@virtuoushub
Copy link
Collaborator

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 trivial can 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.

@virtuoushub
Copy link
Collaborator Author

[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
This was referenced Nov 19, 2014
@virtuoushub
Copy link
Collaborator Author

lwjgl3 has done a lot of this work already. If implementing this feature definitely give it a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant