Invalid escape sequence \c

[nRF5xFanboy]

Hi All,

Today I am migrating my project from ncs 1.9.1 to ncs 2.0.0.

The project was building find with ncs 1.9.1

But I do got this build warning with ncs 2.0.0:

-- Found Python3: C:/cm/ncs/toolchains/v2.0.0/opt/bin/python.exe (found version "3.8.2") found components: Interpreter

=== child image mcuboot - begin ===
loading initial cache file C:/cm/projects/projectX/build/mcuboot/child_image_preload.cmake
CMake Warning (dev) at C:\cm\projects\projectX\build\mcuboot\child_image_preload.cmake:5 (set):
Syntax error in cmake code at

C:\cm\projects\projectX\build\mcuboot\child_image_preload.cmake:5

when parsing string

C:\cm\projects\my_own_modules\nrf52_fanboy_SDK

Invalid escape sequence \c

Policy CMP0010 is not set: Bad variable reference syntax is an error. Run
"cmake --help-policy CMP0010" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.

Loading Zephyr default modules (Zephyr base (cached)).


...



CMake Warning at C:\cm\ncs\v2.0.0\zephyr\CMakeLists.txt:814 (message):
  No SOURCES given to Zephyr library: drivers__console

  Excluding target from build.


-- Configuring done
-- Generating done

Any idea / hint / tip how to fix this correctly.

[Einar Thorsrud]

Hi,

I get a feeling there is something wrong with the environment. Does building sample projects work? If not (or in any case really), can you try to re-install 2.0.0 from the Toolchain manager? Also, open VS Code from the toolchain manager to ensure that it is configured correctly with the path to the SDK source code and toolchain.

[nRF5xFanboy]

Hi Einar,

Thanks for your reply.
I already noticed that opening vscode not from the nrf connect sdk toolchain manager means trouble.
Therefore i remove all pinned to startup / shortcuts / pinned to taskbar etc that directly start vscode from windows  where possible - one shortcut link remains nrfConnect  - it means more clicks but that is OK.

To answer you question "does building samples work?" fine yes.

I already discovered that the transition from ncs 151 with SES towards ncs191/200 with VScode also impacts more than expected.
with SES the cmaketext was  a place to place settings i noticed during transition we need to re-locate some of this settings to vscode to control the build process in correct way.

Shure I can reinstall ncs2.0.0
and try again

Best regards,
    nRF5xFanBoy

[Einar Thorsrud]

Hi,

nRF5xFanboy said:

To answer you question "does building samples work?" fine yes.

OK, that is good. Then perhaps this is just an issue with migrating your specific application. I must admit I did not make much sense of the error log. Have you had a look at some similar sample project files and compared? If no luck, perhaps you can upload your project files here so we can have a look? Also explain how you build them, for instance if you add some additional parameters (on the command line or via build configuration GUI in nRF Connect for VS Code)?

nRF5xFanboy said:

I already discovered that the transition from ncs 151 with SES towards ncs191/200 with VScode also impacts more than expected.
with SES the cmaketext was  a place to place settings i noticed during transition we need to re-locate some of this settings to vscode to control the build process in correct way.

VS Code itself does not impact the build process (it essentially just run west with some arguments, which in turn runs CMake, ninja etc for you).