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

Dotnet Tools #589

Open
wasabii opened this issue Sep 4, 2024 · 1 comment
Open

Dotnet Tools #589

wasabii opened this issue Sep 4, 2024 · 1 comment

Comments

@wasabii
Copy link
Contributor

wasabii commented Sep 4, 2024

We should expose Dotnet tool packages. Two obvious ones are ikvmc and ikvmstub. I do think we should go through with the remain to ikvmimp and ikvmexp at this point. Perhaps exposed as subcommands of a singleular tool: 'dotnet ikvm export', 'dotnet ikvm import', etc. Or some similar pattern.

Additionally, our JRE/JDK distribution, should be distributed as tools. This would make it easy for .NET users to install our JDK and just start using it.

'dotnet ikvm java', 'dotnet ikvm javac'. Etc.

@wasabii
Copy link
Contributor Author

wasabii commented Sep 4, 2024

We probably should think through how we can make it a bit easier to specify things like IVKM.java, IKVM.Runtime and the BCL with these tools though. And whether any information that is available to us by being a dotnet tool can assist with that. Can we, for instance, actually deliver Framework reference assemblies with the tools? How do we deal with cross-tfm problems still? We still need a separate tool version for Framework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant