You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the crucible-jvm executable allows specifying the locations of Java classes through the -j flag (for JAR files) and the -c flag (for .class files). This has two issues:
For JDK 8 and earlier, this requires finding where your JDK installation's rt.jar file is and manually passing it to crucible-jvm. This is tedious.
Elsewhere, SAW aims to fix these issues with GaloisInc/saw-script#1030, which adds a -b flag which points to the location where the java executable lives. (Alternatively, if -b isn't set, SAW can also find java if it is located on the PATH.) With this information, one doesn't need to specify where rt.jar lives at all, as it can be inferred from java -XshowSettings:properties. Moreover, knowing where java is located is essential to getting JDK 9 and later to work.
I propose we adopt a similar -b/PATH scheme for crucible-jvm.
The text was updated successfully, but these errors were encountered:
This mirrors a similar recent change introduced to SAW in
GaloisInc/saw-script#1030.
While I was in town, I updated the two `crucible-jvm`–related test suites
to use the `PATH` instead of the `-j` flag. I can't exactly confirm via CI
if these changes work (see #634), but they appear to do the right thing
locally.
Fixes#633.
Currently, the
crucible-jvm
executable allows specifying the locations of Java classes through the-j
flag (for JAR files) and the-c
flag (for.class
files). This has two issues:rt.jar
file is and manually passing it tocrucible-jvm
. This is tedious.Elsewhere, SAW aims to fix these issues with GaloisInc/saw-script#1030, which adds a
-b
flag which points to the location where thejava
executable lives. (Alternatively, if-b
isn't set, SAW can also findjava
if it is located on thePATH
.) With this information, one doesn't need to specify wherert.jar
lives at all, as it can be inferred fromjava -XshowSettings:properties
. Moreover, knowing wherejava
is located is essential to getting JDK 9 and later to work.I propose we adopt a similar
-b
/PATH
scheme forcrucible-jvm
.The text was updated successfully, but these errors were encountered: