Invalid escape sequence \c

RE: Invalid escape sequence \c

Einar Thorsrud — Fri, 05 Aug 2022 08:59:45 GMT

Hi,

[quote user="nRF5xFanboy"]To answer you question "does building samples work?" fine yes.[/quote]

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)?

[quote user="nRF5xFanboy"]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.[/quote]

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).

RE: Invalid escape sequence \c

nRF5xFanboy — Fri, 05 Aug 2022 06:26:52 GMT

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

RE: Invalid escape sequence \c

Einar Thorsrud — Thu, 04 Aug 2022 13:05:26 GMT

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.

RE: Invalid escape sequence \c

nRF5xFanboy — Tue, 02 Aug 2022 11:00:04 GMT

Hi All,

I also see this pop-up in MS visual Code (upon opening) when I do build my migrated project with ncs 2.0.0

Any idea / hint / tip how to fix this correctly?
Thanks in advance