Skip to content

Conversation

@MeFisto94
Copy link
Member

So we need to depend on the assemble target, as build only happens when the project is additionally tested, which it might be for CI, but not when including as a subproject (like the SDK did) and also not when calling gradlew run, which one would do when executing the jme tests.

I've taken the freedom to run an auto formatter on that snippet as well to fix whitespaces, I hope you don't mind. It just looked like minified js to me ;)

…g from cpp source and not using the build target.
@MeFisto94
Copy link
Member Author

Note: there is still a flaw in this build: the -sources jar also contains the built natives ALONG with the native sources.

Copy link
Member

@riccardobl riccardobl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine. Thank you

@riccardobl
Copy link
Member

Note: there is still a flaw in this build: the -sources jar also contains the built natives ALONG with the native sources.

Mhh, can you open an issue for that?

@MeFisto94 MeFisto94 merged commit 933b091 into jMonkeyEngine:master Jan 13, 2020
@MeFisto94
Copy link
Member Author

I've taken the freedom to self-merge this, given that the review was positive and that it's urgent as the SDK and the jme tests needed this commit to work :)

@MeFisto94 MeFisto94 deleted the fix-bullet-natives branch February 6, 2020 00:28
@stephengold stephengold added the buildscript An issue with the buildscript label Mar 13, 2021
@stephengold stephengold added this to the v3.4.0 milestone Mar 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

buildscript An issue with the buildscript

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants