zed/script/download-rust-analyzer

#!/bin/bash

set -e

export RUST_ANALYZER_URL="https://github.com/rust-analyzer/rust-analyzer/releases/download/2021-10-18/"

function download {
    local filename="rust-analyzer-$1"
    curl -L $RUST_ANALYZER_URL/$filename.gz | gunzip > vendor/bin/$filename
    chmod +x vendor/bin/$filename
}

mkdir -p vendor/bin
download "x86_64-apple-darwin"
download "aarch64-apple-darwin"

cd vendor/bin
lipo -create rust-analyzer-* -output rust-analyzer
rm rust-analyzer-*
Implement a more robust way of locating rust-analyzer When bundled, we will retrieve it out of the `Resources` folder. Locally, we're expected to run `script/download-rust-analyzer` and put `vendor/bin` in our $PATH. 2021-10-25 09:02:35 +00:00			`#!/bin/bash`

			`set -e`

			`export RUST_ANALYZER_URL="https://github.com/rust-analyzer/rust-analyzer/releases/download/2021-10-18/"`

			`function download {`
			`local filename="rust-analyzer-$1"`
			`curl -L $RUST_ANALYZER_URL/$filename.gz \| gunzip > vendor/bin/$filename`
			`chmod +x vendor/bin/$filename`
			`}`

			`mkdir -p vendor/bin`
			`download "x86_64-apple-darwin"`
			`download "aarch64-apple-darwin"`
Move lsp configuration into language crate Co-Authored-By: Nathan Sobo <nathan@zed.dev> 2021-10-26 19:17:51 +00:00
			`cd vendor/bin`
			`lipo -create rust-analyzer-* -output rust-analyzer`
			`rm rust-analyzer-*`