a way to give RLS environment settings

[Geobert]

Some month ago, I faced some weird bugs in VSCode with extension stop working (no reference, no completion, no occurrence). I don't know how it was possible that it has ever work before as the fix was to launch VSCode in a shell with the environment being set, via a batch file:

@echo off
call "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvarsall.bat" x86_amd64
start "" code %*

So RLS has the proper MS tools to work with.

It's not very convenient nor straightforward and I'm opening this issue to try to improve RLS on this matter.

Any thought?

Thank you for reading :)

[nrc]

To be clear, you want a way to set environment variables passed to the RLS from VSCode? If so that is a fairly easy change to the VSCode plugin. Happy to give instructions if you want to make a PR.

[Geobert]

I don't know, is VSCode capable of loading a bat file to configure it's environment once it has been launched? As for a PR, I don't know Typescript nor Javascript at all (last time I've done something in JS was in the 90's to make stuff on mouse over… so you got an idea of my level in these languages ^^')

[nrc]

Would it be enough to take a list of env vars and values and set them in the extension, rather than running a bat file?

[Geobert]

I may be enough, I'm not sure, the bat file is pretty big:
vcvarsall.zip

[vimmerru]

My use case:

• I need to build project that uses libsodium, openssl, zmq and similar native libraries
• On windows -sys crates asks for environment variables with libraries placement like OPENSSL_DIR, SODIUM_DIR and etc

For now i don't have clear way how to provide this environment to RLS. It just says "Can't compile external crate" and no any features works

[ray-kast]

Here's a quick 'n' dirty fix for setting RLS environment variables on Linux:

(it's essentially just launching VSCode itself with the variables exported)

export OPENSSL_INCLUDE_DIR=/usr/include/openssl-1.0
export OPENSSL_LIB_DIR=/usr/lib/openssl-1.0

code .

It's not a great fix (or a viable long-term solution by any means), but it works.

[Xanewok]

I don't think we should support an ad-hoc way to specify the environment inside the RLS itself - this doesn't solve the case of wrapper scripts (you wouldn't expect to run the vcvars and copy them over to some config file)

I believe how you invoke RLS should be configured by the editors with rls-vscode supporting rlsPath config (which I also use to run a custom RLS for development).