@borkdude why did you close https://github.com/lread/clj-graal-docs/issues/4 - i am trying to figure out why a particular project can be built (and run) using your uberjar method, but fails when using clj.native-image

@sogaiu Now the observed difference is gone in the hello world version of that repo

I don't exactly remember the details, it was just a temporary issue for something I was figuring out

one issue I've had with clj-native was the order in which things were compiled or that not all the source was compiled

so that could be your problem

thanks for the hints -- my quest continues 🙂

what is the error you're getting

@borkdude i get multiple of this type of thing:

Error: Unsupported features in 12 methods
Detailed message:
Error: com.oracle.graal.pointsto.constraints.UnresolvedElementException: Discovered unresolved type during parsing: clojure.tools.reader.reader_types.IPushbackReader. To diagnose the issue you can use the --allow-incomplete-classpath option. The missing type is then reported at run time when it is accessed the first time.
Trace: 
	at parsing rewrite_clj.reader$unread.invokeStatic(reader.clj:115)
Call path from entry point to rewrite_clj.reader$unread.invokeStatic(Object, Object): 
	at rewrite_clj.reader$unread.invokeStatic(reader.clj:112)
	at rewrite_clj.reader$unread.invoke(reader.clj:112)
	at clojure.lang.AFn.applyToHelper(AFn.java:156)
	at clojure.lang.AFn.applyTo(AFn.java:144)
	at script.main(Unknown Source)
	at com.oracle.svm.core.JavaMainWrapper.runCore(JavaMainWrapper.java:151)
	at com.oracle.svm.core.JavaMainWrapper.run(JavaMainWrapper.java:186)
	at com.oracle.svm.core.code.IsolateEnterStub.JavaMainWrapper_run_5087f5482cc9a6abc971913ece43acb471d2631b(generated:0)

@sogaiu can you compare the .class files in the uberjar to the .class files produced by the clj native tool?

if there's a difference, it's probably that

i'll take a look (iiuc IPushbackReader comes into existence via defprotocol -- is that something that can be understood by native-image at build time?)

I think so yes, as long as the protocol is defined at compile time

I'm using this in babashka as well

ok, thanks

top level I mean, defined during the native image analysis

so far in the comparison, it appears that via lein i get some class files (as well as the source) for tools.reader.reader_types, but i don't see anything in the classes directory for clj-native-image -- that looks relevant < @taylor

the weird thing is that this used to work

it works up through this commit: https://github.com/taylorwood/clj.native-image/commit/7773c73886a5938fec2d6c5a2227c1aec686e1a5 it stops working here: https://github.com/taylorwood/clj.native-image/commit/b3823a48be75122b9671c86ce5353a85589ef15f changing the tools.namespace version seems to trigger the issue

I've had a similar problem, that's why I went to lein eventually, since that has more predictable compilation

btw, I also had a script somewhere to compile all namespaces

let me see if I can find it, but that will be later, since I'm cooking dinner right now

fwiw I can't find it anymore, I think I deleted it while making a hello world for clj-graal-docs and I didn't need it anymore

but it used tools.namespace to list all namespaces

np -- thanks for considering 🙂

and then ran compile on it manually

it seems odd because the part of tools.namespace that clj.native-image is using is just find-namespaces-in-dir -- i've compared the values for both versions of tools.namespace (the one from the version of clj.native-image that works from the one that doesn't) and they return the same value.

there is only one value in both cases, and it is script

so iiuc, there is only one invocation of compile

https://github.com/taylorwood/clj.native-image/blob/master/src/clj/native_image.clj#L89_L94

(let [deps-map (merged-deps)
      namespaces (mapcat (comp find-namespaces-in-dir io/file) (:paths deps-map))]
  (prep-compile-path)
  (doseq [ns (distinct (cons main-ns namespaces))]
    (println "Compiling" ns)
    (compile (symbol ns)))

What is the current situation of making native images which use AWS SDK? It seems that Amazonica seems to not work but have anyone tried Cognitects AWS SDK?

why does it not work? reflection?

if it's that, you can make it work using a reflection config