nrf Connect Terminal LD_LIBRARY_PATH problem

[Reid666]

nrf Connect Terminal overwrites LD_LIBRARY_PATH. I have added SEGGER JLink path to it so nrfjprog and JLink can dynamically link to the JLink dot so files. This works on Bash and ZSH outside nrf Connect terminal. 

Please see the screenshots below from the terminal window in VSCode:

I have found below template hoping that I can somehow insert JLink library path:

"nrf-connect.terminalProfile.shell": {

"path": "/usr/bin/zsh",

"args": []

},

however I'm not sure whether LD_LIBRARY_PATH is append-able for nrf Connect Terminal. How can I fix this problem ? 

[Reid666]

I still have the same problem:

nrfjprog -v
[error] [SeggerBackend] - Error in dlopen: libjlinkarm.so: cannot open shared object file: No such file or directory
[error] [ Worker] - Dll failed to open.
[error] [ Client] - Encountered error -101: Command open executed for 11 milliseconds with result -101
ERROR: JLinkARM DLL load failed. Try again. If it keeps failing, please
ERROR: reinstall latest JLinkARM from Segger webpage.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

[Sigurd Hellesvik]

Good to know.

Try nrf-connect.west.env. If this does not work, I will report what you see to the devs as a bug.

[Reid666]

It did not work. I have below configs:

[Sigurd Hellesvik]

I have contacted our VS Code Extension devs and will let you know when I know more.

[Sigurd Hellesvik]

Our devs say that "As of now we don't have a solution for this". Luckily the normal JLink install method works, so this is kindof a corner case.

Devs also suggest a possible workaround:

"
Alternatively there's a hack, it might be possible to manipulate the toolchain itself: /PATHTO/ncs/toolchains/b81a7cd864/environment.json, but be aware this must be done with care and for each toolchain used. Also the change won't be kept when reinstalling the tarmandoolchain, so this will be a temporary workaround.
"