Since it is a flake, you can use something like this to get it started: nix run "git+" -- --help This will run native-image for graalvm11-ce with support for musl (and musl only, glibc builds are broken)

If you use nix run "git+" -- --help, this will run native-image for graalvm11-ce and glibc (no musl support)

If you want to have a quick shell with graalvm11-ce and all binaries, nix develop ""git+" should work

that's amazing! great work!

Moved to: https://github.com/thiagokokada/graalvm-nix

If that works well, maybe @U04V4KLKC could think on making the Github actions use this? as it's pure

@UJ1339K2B Are you sure this is in data.xml? I'm using this in bb and I didn't have to do this. Are you sure your code or one of your libs doesn't instantiate any XML things on the top level?

I'm just trying to confirm it in graal-config. The code I tried to compile is using cognitect aws api, but I'm not seeing any usage of data.xml on top level. see: https://github.com/cognitect-labs/aws-api/blob/master/src/cognitect/aws/util.clj

why don't you just add .apache.xerces and javax.xml

Shouldn't we specify only the classes that the particular library use instead of saying "build all the classes from the namespace xyz"?

Btw found a reflection as well:

(defn -main
  [& _args]
  (println (xml/parse-str
            (xml/emit-str (xml/sexp-as-element
                           [:foo {:foo-attr "foo value"}
                            [:bar {:bar-attr "bar value"}
                             [:baz {} "The baz value"]]])))))

Exception in thread "main" java.lang.IllegalArgumentException: No matching method createXMLStreamReader found taking 1 args for class com.sun.xml.internal.stream.XMLInputFactoryImpl

Optimally yes, but previously you also initialized everything at build time so this is already an improvement ;)

I think we can make a fork of this lib to be honest, to yield much smaller graalvm binaries

the dynaload thing is causing image bloat

but it wasn't high on my list since it doesn't affect bb directly, only the pod

this library is just one glorified http call library mostly

that should not take 100mb

I think the size can be reduced to 30mb or so

Eh. As always you are right. This has something to do with aws api. I will trace the initialization.