Porting to NCS v2.0

[dboling]

Our development environment extends the NCS for our 9160 and 52840 hardware. To create a command line build environment in v.1.x.x, I was able to leverage the env.cmd file found in .\v1.x.x\toolchain\cmd to set the environment variables needed by command line builds. This isolated our tools from having to know and individually set these variables.

Now, in v2.0, this cmd file no longer exists. The only way to get an 'official' command line build environment appears to be to use the "Toolchain Manager" GUI tool. Is there a documented way to set the proper environment variables from the command line? Thanks.

Doug

[mytzyiay]

Don't know if this is correct, but it worked for me:

I never needed that CMAKE_PREFIX_PATH variable before v2.0.0.  And the toolchain never used to live under /opt/nordic/ncs/toolchains either.

[dboling]

Thanks, my issue is that I would like Nordic to restore the NCS version and OS independent command line configuration file.
It's important that Nordic provide command line alternatives for all their GUI tools.