Asset Tracker build problem

[Damion]

Good day.

I am busy evaluating the nRF9160, but when he builds his project he's getting the following error.

mkdir(modules/nrfxlib/nrf_security/src/mbedtls/CMakeFiles/mbedtls_external.dir/C_/Users/greg.gallagher/Documents/xxxxx/Projects/xxxxx): No such file or directory

I then zipped my whole ncs folder and sent it to him, but when he builds his project it comes up with the same error.

Is there something that we can suggest he try to fix the problem?

Regards

Damion

[Øyvind]

Hello Damion, 

Has your client done anything to his NCS install, or is it a clean install using the Getting Started Assistant? Is the Asset Tracker application untouched? In SES, what does nRF Connect Options look like (Tools --> Options --> nRF Connect)

Kind regards,
Øyvind

[Damion]

Hi Øyvind.

Thanks for your fast reply.

It was a clean install using the Getting Started Assistant.

When he downloaded it form Git it was untouched. Mine however has a few extra lines of code to force it to band 8, use NBIoT & GPS, use Vodacom-SA APN and has a static IP address for nRF cloud.

I helped him with the setup, so his looks the same as mine except for the location of his ncs folder. We have checked that his path has no spaces too.

Regards

Damion

[Øyvind]

Damion said:

It was a clean install using the Getting Started Assistant.

 Ok, this should be fairly straight forward. Is the customer using the master branch or tag v1.2.0?

Damion said:

Mine however has a few extra lines of code to force it to band 8, use NBIoT & GPS, use Vodacom-SA APN and has a static IP address for nRF cloud.

 He should be able to build either way,

mkdir(modules/nrfxlib/nrf_security/src/mbedtls/CMakeFiles/mbedtls_external.dir/C_/Users/greg.gallagher/Documents/Snuza/Projects/Snuza)

It looks like the compiler tries to add an extra path to the end. If not able to find the cause, can your customer try to re-init the git repository?

 -Øyvind

  

[Damion]

Hi Øyvind.

 

Øyvind said:

Is the customer using the master branch or tag v1.2.0?

He is using the v1.2.0 tag.

 

Øyvind said:

If not able to find the cause, can your customer try to re-init the git repository?

I will ask him to do so and get back to you.

Thanks for the help.

Regards 

Damion

[Damion]

Hi Øyvind.

We finally got his code to compile, it was his directory path that was too long.

I saw in the error message that it didn't list his full path and then compared it to mine.

He moved his whole folder to the root and then it worked.

Thanks for your assistance.

Regards

Damion.