How to setup VSC nrf connect to recognise my forked SDK repositories.

RE: How to setup VSC nrf connect to recognise my forked SDK repositories.

Håkon Alseth — Wed, 04 Dec 2024 10:26:05 GMT

Hi,

You could have a look at the example application in zephyr:

https://github.com/zephyrproject-rtos/example-application

This will point to the sdk remote:

https://github.com/zephyrproject-rtos/example-application/blob/main/west.yml#L10

Kind regards,

Håkon

RE: How to setup VSC nrf connect to recognise my forked SDK repositories.

Logicomwk — Tue, 03 Dec 2024 01:01:51 GMT

Thank you for the response and the update link.

If I keep a fork of the repository on my github account. Is there documentation on how I can use my forked repository with VSC and nRF Connect in the Freestanding mode. i.e. my application lies outside the NCS SDK. I believe this is how VSC and nRF Connect work in the default case.

I was able to perform the steps in Workflow 4 (from your link above)

RE: How to setup VSC nrf connect to recognise my forked SDK repositories.

Håkon Alseth — Mon, 02 Dec 2024 14:11:51 GMT

Hi,

Your link points to the very first release (v0.3) of NCS. Here's an updated link:

https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/dev_model_and_contributions/adding_code.html

[quote user=""]I have to make changes to some USB files in the v2.6.0 SDK and these files will need to be shared with 2 other developers.[/quote]

The easiest way to share what differs is either to share the commit itself, and cherry-pick, or that you keep a fork of the SDK with these changes already present.

Another alternative is to provide a diff/patch of your changes:

cd path/to/ncs/<repo>

git diff > my_changes.diff

And apply this via "git apply my_changes.diff".

Kind regards,

Håkon