Skip to content
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

Run script or project with graalvm's automatic metadata collection via the tracing agent #3222

Open
Flowdalic opened this issue Oct 4, 2024 · 1 comment
Labels
enhancement New feature or request GraalVM Issues tied with GraalVM native images

Comments

@Flowdalic
Copy link
Contributor

There is already good support to build a native image using graalvm via scala-cli. However, many applications require a native-image configuration due to the dynamic features of Java. Creating those configuration files by hand can become a complex task.

Luckily, graalvm allows to automatically generate the native-image configuration by tracing the application.

It would be great if scala-cli run would grew a --native-image-trace [out-dir] option that results in out-dir becoming populated with the native-image configuration. If out-dir is unspecified, it probably should default to the current working directory.

Even though it is possible that the resulting configuration is incomplete, because the program did not exhibit a certain behavior during the trace, it would be still a good starting point.

@Flowdalic Flowdalic added the enhancement New feature or request label Oct 4, 2024
@lbialy
Copy link

lbialy commented Oct 5, 2024

It should be available on both run and test and use the merge variant of the graalvm commands underneath not to overwrite traces gathered in test vs run.

@Gedochao Gedochao added the GraalVM Issues tied with GraalVM native images label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request GraalVM Issues tied with GraalVM native images
Projects
None yet
Development

No branches or pull requests

3 participants