-
-
Notifications
You must be signed in to change notification settings - Fork 166
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better JVM detection #494
Better JVM detection #494
Conversation
nvm, gonna delete the profile thing. It's getting ignored 馃槶 |
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.
haven't tested it, but seems fine. Double check that the comments on line 301 are intended to be commented out @ImUrX
4c5e2f5
to
f8eb8fd
Compare
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.
LGTM, though you might want to consider inspecting/respecting the JAVA_HOME environment variable at some point.
b0e98e8
to
8cb25b8
Compare
Co-authored-by: Ryan Butler <thebutlah@gmail.com>
Co-authored-by: Ryan Butler <thebutlah@gmail.com>
051b818
to
9619ca9
Compare
this is ready for merge |
Added conditionals depending on OS, now Linux does it's own JVM detection based on
/usr/lib/jvm
.Also left a macOS one because it makes the
#[cfg()]
a lot cleaner and I just need to actually test it (I know where macOS saves them but I still want to test it).I prioritized the
APPDIR
env just in case, because if we are using AppImage, we should trust the jar we have instead of a relative dir one.I also kind of crept in some optimizations on the release build for less bin size... 馃憖