-
Notifications
You must be signed in to change notification settings - Fork 12
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
CI workflow: fix relative cargo.toml path after gradle upgrade to 8.12 #340
Conversation
@@ -208,7 +208,7 @@ fun buildZenohJNI(mode: BuildMode = BuildMode.DEBUG) { | |||
} | |||
|
|||
val result = project.exec { | |||
commandLine(*(cargoCommand.toTypedArray()), "--manifest-path", "../zenoh-jni/Cargo.toml") | |||
commandLine(*(cargoCommand.toTypedArray()), "--manifest-path", "./zenoh-jni/Cargo.toml") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a number of other places in the file that uses the relative path ../
, shouldn't those be updated as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like CI passes with just the one change in the relative dir. I wonder if it might cause problems during release though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have double checked doing publications to maven local and the native libs are loaded properly. Seems that the Gradle upgrade issue only affects here when running a command this way using commandLine (which is a trick for automatically building the native library before building the packages). These changes should work fine.
No description provided.