How to set up VScode for eternal build

RE: How to set up VScode for eternal build

Randy Lee — Mon, 13 Nov 2023 13:31:10 GMT

Check this out: https://mcuoneclipse.com/2023/11/11/vs-code-cure-the-extension-creep-with-profiles/ Might be at least a partial solution to the problem.

RE: How to set up VScode for eternal build

Randy Lee — Wed, 08 Nov 2023 13:39:54 GMT

well, that's an option... Complicated but an option. Thanx for pointing to it. I like this documentation because it exposes the underlying structures and, therefore, assumptions.

Reading through all this it strikes me as how ridiculously complicated all this setup is. All of this is obviously designed by a [lazy] committee.

Apparently no one actually understands simple these days. Certainly not the people at Zephyr. There is no reason in the world why this should be anywhere near this complicated to work with. None.

Anyway, thanx for the pointers...

RE: How to set up VScode for eternal build

runsiv — Wed, 08 Nov 2023 08:46:13 GMT

I know.. If you only need to rebuild your application once in a while. You could have a look at doing a manual installation of the NCS. Its not the most user friendly. But if you only need to rebuild the application you don't need VScode and that is one less thing to worry about.

Regards

Runar

RE: How to set up VScode for eternal build

Randy Lee — Tue, 07 Nov 2023 13:27:58 GMT

thanx.... Sigh. Nothing like very heavy development environments.

RE: How to set up VScode for eternal build

runsiv — Tue, 07 Nov 2023 08:24:00 GMT

Update:
I heard back from our developers. They had the following recommendation. Either create a VM or docker image where you create a west manifest to lock your project to a specific version of the SDK. The process of creating a west manifest or forking the SDK is covered here.

Regards

Runar

RE: How to set up VScode for eternal build

runsiv — Mon, 06 Nov 2023 12:04:43 GMT

Hi Randy

I think there is a few options you can consider:

1. You might fork the NCS repo you are using and use that in the future. However since VScode is not developed by Nordic, we have no control over if it would be possible to download a working version with the correct versions of the extensions in 10+ years time.

2. Create a docker/VM image with a complete setup of the build environment you are using. This is what I think will provide the best solution where you don't have to worry about breaking changes in the extensions or availability of a specific version.

I have also asked our nRF connect developers for input and will update when I hear back from them.

Regards

Runar