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

[Logicomwk]

Hello,

I am using VSC on Windows with nRF Connect.   Previously I have installed the NCS SDK using the "RF Connect" Toolchain manager.

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.

I followed these instructions to create forks

docs.nordicsemi.com/.../gs_ins_fork.html

I placed them in the c:/ncs/my-fork folder.

VSC nRF Connect is currently configured for c:/ncs/v2.6.0

1) What are the steps required to use the forked SDK in "c:/ncs/my-fork)" with VSC and nRF Connect

Simply changing the Topdir (for User or Workspace) does not work.

Wayne

[Håkon Alseth]

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

 

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.

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

[Logicomwk]

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)