Vojin Jovanovic

Yes, this option is not really for end-users as it requires source code.

@pejovica did the AWT for Windows so he can give a better estimate.

I believe the build tools set the `org.graalvm.nativeimage.imagecode` system property and makes `org.graalvm.nativeimage.ImageInfo#inImageCode` behave incorrectly.

Adding @gradinac as he is maintaining static linking with Musl and the distroless feature that we have.

The problem here is that we still mark the whole JDK as build-time by default. The error message is misleading here--I am improving this case in a separate PR. Here...

From the next release (already in master) you can use -H:+TraceClassInitialization to see how this Thread got initialized. You need to use `--initialize-at-build-time` in the right places to prevent this...

@pejovica assigning to you as the problem is in missing native implementations for security functions.

Don't think so, it is just not our priority. If you want, you would probably get it running in a matter of days.

You would need to define which classes should be marked with `--initialize-at-run-time`. The nasty thing is that `-H:+TraceClassInitialization` does not work for most of the JDK so you would have...

You just start building an image and adding a flag by flag that fixes the problems. If you want to invest the time I will guide you through the process.