Fork me on GitHub

Could someone point me to a build configuration (i.e. something like from the hello-world example) that works when using aleph for HTTP client? I seem to be getting a good deal of errors around* classes, with a recommendation from the compiler that I include a --initialize-at-run-time flag for the each offending object. I was hoping I would not have to do each individually but perhaps that is the only way.


additional context: I’m working off of this example, though it seems to be creating a server while I’m using the http client: Not sure if that makes a difference.


@mafcocinco never tried aleph to native, but http-kit 2.5.0 works very well with graalvm. also works cross platform (small wrapper around curl).


Clj-http-lite works well too.


cool. I’ll just use http-kit if it works. thanks.


@mafcocinco babashka already bundles http-kit, so you can also use that as a native client


getting netty to compile for native-image needs that you profile it beforehand with realistic workloads so it knows what gets used


i was analyzing it with -agentlib:native-image-agent=config-output-dir=./resources