Re-installing nRF Connect SDK

[turboscrew]

How do I remove nRF Connect SDK from Windows before re-installing?

And are there something that needs to be done, if you have used cmake and Visual Studio Code for other projects?

I installed the tools via nRF Connect Desktop / Toolchain Manager in a project directory, but it looked like the paths got too long. Then I uninstalled the stuff via nRF Connect Desktop / Toolchain Manager, uninstalled the nRF Connect Desktop, removed the stuff from the project directory and rebooted. Then I re-installed everything at C:/ncs, but when I try to do something, it still defaults to the deleted project directory.

Also, when I tried (after re-install) to create the shell_bt_nus from an example and into another folder, I got the ELF-files (ARM code), but the Visual Studio Code shows errors:

[{
    "resource": "/C:/Users/ett15110/Documents/Projects/xxxy/test/shell_bt_nus/src/main.c",
    "owner": "C/C++",
    "code": "1696",
    "severity": 8,
    "message": "cannot open source file \"alloca.h\" (dependency of \"logging/log.h\")",
    "source": "C/C++",
    "startLineNumber": 17,
    "startColumn": 1,
    "endLineNumber": 17,
    "endColumn": 25
},{
    "resource": "/C:/Users/ett15110/Documents/Projects/xxx/test/shell_bt_nus/src/main.c",
    "owner": "C/C++",
    "code": "1696",
    "severity": 8,
    "message": "cannot open source file \"alloca.h\" (dependency of \"zephyr.h\")",
    "source": "C/C++",
    "startLineNumber": 11,
    "startColumn": 1,
    "endLineNumber": 11,
    "endColumn": 20
},{
    "resource": "/C:/Users/ett15110/Documents/Projects/xxx/test/shell_bt_nus/src/main.c",
    "owner": "C/C++",
    "code": "1696",
    "severity": 8,
    "message": "#include errors detected. Consider updating your compile_commands.json or includePath. Squiggles are disabled for this translation unit (C:\\Users\\ett15110\\Documents\\Projects\\xxx\\test\\shell_bt_nus\\src\\main.c).",
    "source": "C/C++",
    "startLineNumber": 11,
    "startColumn": 1,
    "endLineNumber": 11,
    "endColumn": 20
}]

The first two seems to happen, because __GNUC__ seems to not been defined.

And in the target folder it generated .vscode-file with this content:

{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE"
            ],
            "windowsSdkVersion": "10.0.19041.0",
            "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/BuildTools/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe",
            "cStandard": "c17",
            "cppStandard": "c++17",
            "intelliSenseMode": "windows-msvc-x64",
            "compileCommands": "${workspaceFolder}/build/compile_commands.json",
            "configurationProvider": "nrf-connect"
        }
    ],
    "version": 4
}

I don't think it should use that compiler for anything.

It also found some errors from code for other HW!

Is there a way to "make clean"? I didn't find any.

[turboscrew]

Oops. the .vscode is directory, and the contents is from c_cpp_properties.json.

Oh, and note that some tools (installed for other projects) are in my AppData folder, and added to my PATH.

[turboscrew]

BTW, I also keep getting this:

"File changes watcher stopped unexpectedly. A reload of the window may enable the watcher again unless the workspace cannot be watched for file changes."

[Simonr]

Hi

You should make sure after you uninstall using the toolchain manager that the files are actually removed from the path you have. That might not be the case if you for example have the VS code application open while uninstalling the SDK. Try making sure that all files are indeed deleted before reinstalling to make sure you start out "fresh".

Best regards,

Simon

[turboscrew]

Which path do you refer to?

And are there any registry keys or "hidden" set-up files?

Where did the SDK find the older, project folder path?

Like I mentioned, in the first try I un-installed the tools using toolchain manager, then I uninstalled the toolchain manager and the whole nRF Connect Desktop and then deleted the folder that contained everything, including the SDK, and booted the PC.

When I re-installed, the SDK still defaulted to the old folder. Where did it know such a folder ever existed?

What should I remove to cure that?

And how does it use %PATH% in common system variables? If there is a path to, say, cmake in the common PATH, could that mess up something? How about Git or VS Code, especially if there are different versions of those already installed in the system?

That is: what is "all files". that I need to check?

Removing nRF Connect Desktop with Revo uninstaller gave:

[turboscrew]

After uninstalling, removing the directories and deleting the registry keys, I reinstalled nRF Connect Desktop, and from there I pressed the "install"-button for nRF Connect SDK v1.9.1, and:

Where the heck did it still found the old installation directory?