Change SDK Directory Variable in SES

[GaryD]

Hello,

I have joined a team that is already in development of firmware for their nRF52840 based product.  The team has a Git repository that includes the SDK which I have cloned and downloaded to my PC F: drive under the SDK main directory of F://REPOs/NORDICSDK/...

Their Repo was saved from a location D://Projects/NordicSDK/...

I am using Windows 10 and nRF52840 SDK nRF5SDK1702d674dde.  The SES version is 5.40.

When I build, I get errors that the include files do not exist.  I found that the include files have a predefined $(SDK).. value for the SDK main directory.  I cannot find where to change the predefined $(SDK) value to my development environment.

Can someone direct me to where the $(SDK) value can be set to my F:// drive location?  Unfortunately I do not have a D:// drive on my PC so I cannot duplicate their settings.  I have searched documents and the Devzone but cannot seem to locate the variable.  I apologize that It is most likely very simple but I cannot seem to find it.   Here is a snippet of where this variable is used and I need to modify it to reflect my environment.

Thank you in advance for your support.

Below is an update to the submission: A build error log with the Project Items directory on left

Item 1 on the snapshot: Note that some files seem to be seen by the compiler - others are not

Item 2: The C file cannot be found during the build but right clicking over the file, the "Copy Full Path" option points to the correct new F:// drive location.

Item 3:  I tried to include a new copy of the link using "Add Existing File" to the the nRF Log directory and the build still indicates it cannot find the file even though I added it again.

[GaryD]

Thank you for you response Joakim,

No - the Global Macros field is blank - no settings.  I have now also found that the links to the project C- files also point to the same SDK folder definition.D://Projects/NordicSDK/... during a build instead of the the new F:// drive location of the SDK.  However, if I right-click over the file name the correct location can be copied using the "Copy Full Link".

I updated the post with a new snapshot that shows the issues during a build.  Some of the files are marked with a red x indicating they could not be found.  Some are marked with a check mark indicating they were found during a build.  Right clicking over either the checked or red x marked files provide the correct Full Link to the files.

I believe the original author used one of the Nordic templates that included all of the different features and only the ones referenced are picked up in a build.  That may be why all the references to unused files are still there.

The originator also has created a Git repo that was uploaded to GitLab where I cloned the Git repository.  Could there be an issue with the creation and cloning of the repository?

I am going to ask the originator to zip up the SDK that he has (with our code embedded inside it) and load that on my computer to see if I can do a build.  That may eliminate the possibility of corruption during the SCM process.

Do you have any other suggestions?

Best regards - GaryD

[Joakim Jakobsen]

Hi again GaryD!

I'm sorry about the delay in response here.

Did you figure out a viable solution to solve your issue, or do you need some assistance to solve this?

Br,
Joakim

[GaryD]

We did resolve the issue in 2 ways.  First, I duplicated the file structure on my computer by renaming one of my disk drives to D:\\ and duplicating the file structure.  Second, the author of the Repo changed the way he was defining the directory structure in the SES project options and eliminating the issue.  He had used full directory tree definitions for some includes instead of using the relative positioning using the \..\..\.. relative file location method.