[Feature request] Implement a setting to allow defining a relative or absolute path to the Elixir install dir

[artman41]

Could a setting be added to allow setting a relative or absolute path to the elixir libraries?

There is a change being made to Erlang.mk to allow use of elixir libraries and compiling of elixir code as part of an erlang library.
Part of the implementation pulls elixir down and compiles it as a build dependency of the project.

Because of this, the elixir libraries exist per project and are only compiled when deps are built

As it stands, elixir ls does not seem to work unless Elixir is exported on the path - ideally, it'd be nice to be able to do define a relative path to the elixir libraries so that the only thing required is to reload the vscode window

A similar feature is currently used by erlang ls as a config option in the erlang_ls.config file to define the otp path

[lukaszsamson]

Can you elaborate more on why per project elixir libs are needed. ElixirLS relies on elixir installation available on PATH in the current env or shim managed by asdf/mise/vfox version managers. It uses whatever is available or configured for the current project. Can you point to some documentation on erlang.mk side?