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

Add a new target to generate jvmti.h when build with linter in travis #4605

Closed
wants to merge 1 commit into from

Conversation

MarkQingGuo
Copy link
Contributor

@MarkQingGuo MarkQingGuo commented Feb 5, 2019

A new target(java_spec_headers) is added in build-on-travis.mk

A new target is necessary because it generates jvmti header files. Since we need to generate different jvmti header files for different JDKs and building with linter doesn't depend on extension repository, we have to modify makefiles so that it generates jvmti header files when build with linter.

PRs should be commited in such order:

There are some changes:

  • A new target(java_spec_headers) is added
  • A new recipe of target java_spec_headers is added: it gets java_spec_version from j9cfg.h then uses it as a variable

Signed-off-by: MarkQingGuo [email protected]

A new target is necessary because it generates jvmti header files. Since we need to generate different jvmti header files for different JDKs and building with linter doesn't depend on extension repository, we have to modify makefiles so that it generates jvmti header files when build with linter.

PRs should be commited in such order:

* jvmti.h.m4 which generates jvmti header files(eclipse-openj9#4409)
* changes in extension repositories(JDK8, JDK11, JDK12)
* changes in JDK11(eclipse-openj9#116) in its specific extension repository
* changes in how openj9 are build with linter(eclipse-openj9#4605)

There are some changes:

* A new target(java_spec_headers) is added
* A new recipe of target java_spec_headers is added: it gets java_spec_version from j9cfg.h then uses it as a variable

Signed-off-by: MarkQingGuo <[email protected]>
@MarkQingGuo
Copy link
Contributor Author

@keithc-ca here maybe other changes we need, if we want to build on travis.

@keithc-ca
Copy link
Contributor

I am hoping that #4409 will be updated to handle cmake builds so that this is unnecessary.

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

Successfully merging this pull request may close these issues.

2 participants