-
Notifications
You must be signed in to change notification settings - Fork 4
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
Native bullet library (for JME3.1) is not extracted #22
Comments
The plugin should find all native libs in project dependency jars. Can you add a link to the bullet project so I can have something to test. |
Thanks for your response!
EDIT: You'll need this repository url to be able to fetch it:
The jar that you get from that contains the structure from the screenshot. |
Thanks. I will try to take a look at it this week. |
Were you able to find anything? Or could I somehow configure the plugin differently? |
That repo location returns a 404 - according to the JME3 docs, their artifacts are in JCenter. Using the
So it appears to be finding them all. If you are still having issues I would need a standalone example or a failing test to look at. |
You can test it with my project here on github: https://github.com/Entropy4711/infinite-wars |
I have a lot going on right now, so I am not sure when I will get back to this. |
Hello,
I started using this plugin to create a game using JME 3.1l, which uses some native libraries (like LWJGL, OpenAL, and Bullet Physics). The plugin almost works perfectly - but it isn't able to extract the native libary files from the Bullet jar. I have the impression that it has something to do with the different structure of the bullet jar. The other jars have a flat directory structure, but the bullet jar has many nested directories for each platform and even for 32-bit and 64-bit.
Here is a screenshot of this structure:
Here a log of ./gradlew clean build includeNatives:
The
<mypath>
texts were added by me.Is this an issue with the plugin, or could I somehow configure this?
The text was updated successfully, but these errors were encountered: