-
Notifications
You must be signed in to change notification settings - Fork 81
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 PackageCompile project and compilation script #695
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool to see this!
We actually hope to ship a statically compiled version with the VS Code extension eventually, so experimenting with this right now is super useful.
Does the whole integration with SymbolServer actually work? We are starting a new Julia process there, and rely on package locations and things like...
@ZacLN I think we can merge this in the contrib folder, right?
Have to say, that I couldn't get this to work with Emacs. However, compiled version threw the same errors as non-compiled one. |
So I do think we should probably only merge it if it works :) |
I've only tested against this hand-crafted message:
Response was:
So, the basic functionality is there. |
Turns out that I couldn't run this in Emacs is because of #651. |
Added repo option to script for convenience. |
Rebased commit |
Now running tests before packaging executable. This triggers compilation of package internal functions. Now LanguageServer.jl starts on my machine under one second. |
This PR adds script for package compilation into binary
This PR adds PackageCompiler project that allows to compile LanguageServer into binary file. Compilation script may simplify process for people unfamiliar with PackageCompiler.
This may be used to generate binary releases.