Reorganise the gradle build script
Open
@MohitMaliFtechiz is already working on this.
Since Mar 22, 2023.
- Dominant language
- Java
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
With PR #27 merged we have now working build system and test.
However, the internal structure of the gradle build system is not perfect. For now we have :
- target
generateHeaderFilesFromJavaWrapperwhich generate the headers from the java class definition - target
buildwhich build the jni wrapper. It use the generated header but it doesn't have a dependency togenerateHeaderFilesFromJavaWrapper. - target
createCodeCoverageReportwhich create the test "binary", run it and then generate the code coverage report. But it create the test binary by recompiling the source of the jni wrapper inside itself.
It would be better to have:
- target
generateHeaderswhich generate the headers from the java class definition - target
buildwhich build the jni wrapper. As it needs the generated header, it depends ofgenerateHeaderswrapper. - target
buildTestwhich build the test binary. As it need to use the created jni wrapper (as if it was a simple user of the wrapper), it depends ofbuildtarget. - target
testwhich run the test binary. It depends ofbuildTesttarget. - target
createCodeCoverageReportwhich depends oftesttarget.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.