-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add SVM metadata #349
Comments
Can you share your manual version? Will make it easier to write a generator. |
Here is one that I used for a super simple example, but it is deeply incomplete and not fully correct in many places. Here is the more exact spec about the reflect.json in general: https:/oracle/graal/blob/master/substratevm/REFLECTION.md#manual-configuration Does that help? |
@martinlippert I'm having issues with lsp4j to make clojure-lsp compile with graalvm, could you provide your config please? |
I'm having this error after starting the LSP server:
It seems it's using the |
@ericdallo here is the json config that I created back then to tell the GraamVM native image builder about the necessary reflection data: But it is quite old, so will most likely not be up-to-date with the latest lsp4j version anymore. |
Thank you very much @martinlippert, but I figured it out using graalvm java agent :D |
Awesome, great to hear that!!! |
I think that merging also with the Lemminx files could help to have a better coverage https:/eclipse/lemminx/tree/master/org.eclipse.lemminx/src/main/resources/META-INF/native-image |
When using lsp4j with SVM (Substrate VM from Graal, which is being used when compiling native images) you need to configure the reflective access that lsp4j does at runtime in some metadata. Would be great if lsp4j would ship that metadata out-of-the-box.
An example for that is:
https:/netty/netty/tree/4.1/transport/src/main/resources/META-INF
I have a manually configured (and most likely incomplete) reflection metadata file, but I assume that lsp4j would prefer to generate that somehow from the protocol.
The text was updated successfully, but these errors were encountered: