Building without NodeJS/WASM

[fruffy]

I would like to try out the language server with my Sublime/Vim-LSP setup instead of VSCode. Is it possible to build the server executable using only Rust's cargo? Or is the NodeJS/WASM setup always required?

[AndrewF001]

NodeJS isn't a requirement if you're not interested in the .vsix file, as the Rust competent can be compiled and run independently. The WASM is a separate cargo, so to avoid building it, you can run this command: cargo build --bin p4analyzer --release, and the executable will be created at target\release\p4analyzer.exe.

We haven't tested how the program interacts with other editors, but it uses the LSP 1.17 standard of communication through stdin & stdout. Please keep in mind that this project is very early stages, so not many features have been implemented, but let me know if you have any issues compiling the project!

[fruffy]

Great, thanks for the prompt reply!

[fruffy]

To install the binary in the cargo folder I had to run cargo install --bin p4analyzer --path crates/p4-analyzer/. Is this the right/intended command?

[AndrewF001]

I believe cargo install will only add it to the Create install list which is used for the Rust Cargo package manager. Cargo build should create a self-contained executable which can be called by Sublime/Vim-LSP. I'm a bit out of my depths but something like this should work for Sublime?:
Open Preferences > Package Settings > LSP > Settings and add "P4Analyzer" client configuration to the "clients":

{
    "clients": {
        "p4-analyzer": {
             // enable this configuration
             "enabled": true,
             // the startup command -- what you would type in a terminal
             "command": ["PATH/TO/p4analyzer", "Create-a-CLI-command"],
             // the selector that selects which type of buffers this language server attaches to
            "selector": "source.p4",
        }
    }
}

[fruffy]

Oh, I was just wondering whether you had a standard way to install the binary generated by cargo build in an install folder. For example ~./local/bin, /usr/local/bin, or ~/.cargo/bin. The command I used seems to work.

Yes, the sublime config should work. If I have some time, I will try to create a package for it.

[AndrewF001]

Glad it worked for you! If you have the time, let me know how it goes. I have created an issue based on this discussion (#28) if you want to contribute!