This popped up about a week ago. Maybe it's helpful: oracle/graal#1679
I take it the properties at build are not hardcoded in the image? It could not see jruby.home after the image was made
ah yeah that's for checking if I'm running in a native image
I need to know if I'm building for a native image so I know to do extra heap setup
it's fine, I'll use my own prop
just a really long command line
Here's the TruffleRuby one: https://github.com/oracle/truffleruby/blob/master/mx.truffleruby/native-image.properties
https://www.graalvm.org/docs/reference-manual/aot-compilation/ has reference to
NATIVE_IMAGE_CONFIG_FILE. That should get you going without mx.
I just came across this article on using maven to drive all this: https://medium.com/graalvm/simplifying-native-image-generation-with-maven-plugin-and-embeddable-configuration-d5b283b92f57
NB: I haven't actually tried either. But both look like promising sources.
most of remaining issues are getting things in the right places so that native-image can see them (psych jar, openssl jar, jffi binary) and then I think things will largely work fine
Hi! The nightly builds are not accessible: https://www.jruby.org/nightly links to https://repo.aws.oss.sonatype.org/content/repositories/snapshots/org/jruby/jruby-complete/ which gives a 404 error page.
Oh but the jar isn't there
Well that's strange, the nightly snapshot job disappeared
Afternoon/Morning. I have this project: https://github.com/fidothe/saxon-rb which wraps the Saxon Java library. We vendor a specific version of Saxon in to the gem with jar-dependencies. There's a mechanism to use different Saxon JARs if you need them (for an older version, or for the EE version). That has worked fine. I just came to use it again to test something and I am getting StackOverflow errors. I have a simple example gist at https://gist.github.com/fidothe/5247bb8236e6dcd42d6bbc1d1b63ad2f showing what's needed. All the loading code is in
lib/saxon/loader.rb.
At this point I'm really not sure if this is a bug in my code or a problem somewhere else
I will check with a JRUBY nightly and see
I will open an issue later this evening, once I get home. Hopefully it's just me doing something dumb.
I'd tested the ability to load other versions of Saxon by loading a SaxonPE version
which has a different JAR name
So I imagine that despite having not required any of the
jar_dependencies stuff on the code path that loads an external Jar, trying to load another version of the Saxon HE jars causes a horrendous pile up because the jar_dependencies vendors the Jars under lib, and so on the $LOAD_PATH
So, this is probably one to take up with @mkristian on the
jar_dependencies repo issues list...
(I have checked, and current code example will load an external Saxon PE jar fine)
Yeah, if you think it is related to jar-deps then file it there, but filing on main JRuby repo is fine too
Do you have a stack trace gist handy?
@headius, better reproduction with a non-1-line stacktrace at the updated https://gist.github.com/fidothe/5247bb8236e6dcd42d6bbc1d1b63ad2f
Will file an issue. Not sure there's a simpler reproduction than to clone my project and grab the external JAR, alas.
@fidothe Thank you!
@donv It seems like jruby-complete jars started snapshotting again 🤷♂️