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

[dboling]

I just discovered another change to v2.0.0 which is not helpful.

The toolchain manager now keeps a record of the NCS installs in the Windows registry. Today, I discovered my v2.0 chain had been corrupted. In the past, I would rename the v2.0.0 directory to v2.0.0_bad, go to the toolchain manager and download a new copy.

However, now the toolchain manager still 'thinks' the v.2.0.0 install continues to exist, and there is no way to download a new copy. Worse, the buttons to open a command line prompt simply fail.This is expected in my case because I manually renamed the directory but others may not understand what is going on.

I solved the problem by instructing the toolchain manager to install v.2.0.0 in a completely different folder and manually moved the directories. However, now the toolchain manager thinks that new install exists. I have found the Windows registry entry for this but I worry that simply deleting that key would result in other problems.

I would expect the toolchain manager to check for the existence of the directories and if not found, at least provide a 'fix' command.

Doug

[Priyanka]

Hi Douglas,

Could you try deleting all previous installations and installing a fresh one? Does it still have the problem?

-Priyanka

[dboling]

My system has to maintain support for a large number of NCS versions as each new version has breaking changes. Therefore, I can't simply delete all my past versions of the NCS.

The problem isn't with other installs. It is with the fact that the Toolchain Manager now using a registry key to decide what versions of the NCS are installed.

Doug

[Priyanka]

I have reported this internally and will get back to you as soon as I get a reply. Kindly expect a delay owing to the vacation period here.

-Priyanka