graalvm 2022-05-22 | Slack Archive

Fork me on GitHub

grounded_sage07:05:47

Is there a way to check at build time if you are building a GraalVM native image?

phronmophobic08:05:38

You can use the static methods on the ImageInfo class, https://www.graalvm.org/sdk/javadoc/org/graalvm/nativeimage/ImageInfo.html

phronmophobic08:05:49

Although you may also want to have different code paths at compile time (eg. building an uber jar). For that, it's common to use System properties. See https://github.com/cnuernber/dtype-next/blob/master/src/tech/v3/datatype/graal_native.clj https://github.com/cnuernber/dtype-next/blob/master/src/tech/v3/datatype/graal_native.cljfor an example

grounded_sage08:05:22

Oh yea the different code paths when building Jar makes sense

borkdude09:05:13

@U05095F2K You can check system properties for this.

borkdude09:05:12

https://stackoverflow.com/a/50291759/6264

borkdude09:05:35

So:

(System/getProperty "com.oracle.graalvm.isaot")

should do the trick and will not couple your program to any of the graalvm specific classes

grounded_sage09:05:50

Found that this does not appear to be working when working on Datahike stack. https://github.com/replikativ/superv.async/blob/5c1ac415b9642e5fb53dccca939dd1a9d44b76ad/src/superv/async.cljc#L101

grounded_sage09:05:46

I'll play with these responses when I am back at computer.

grounded_sage09:05:07

Actually just realised I build the jar and then the native image. So of course it's not there at macro expansion.

👍 1