nRF Connect SDK broken for nRF9160 command line build on Windows

[Gregor Bader]

Since Commit https://github.com/NordicPlayground/fw-nrfconnect-zephyr/commit/bd7569f272882f105515acda04e45e7878a68e13
the cmake build on Windows is broken (see also https://devzone.nordicsemi.com/f/nordic-q-a/45543/issue-with-command-line-compilation-of-nrf9160-samples ).

This is because the python script zephyr/scripts/zephyr_module.py outputs Windows backslash paths into file build/Kconfig.modules which cannot be process
afterwards by the Kconfig step zephyr/scripts/kconfig/kconfig.py!

With attached patch this can be fixed temporarly.

regards,
Gregor Bader

zephyr_windows_build.patch

[jbrzozoski]

Holy crap, it was just a /-vs-\ bug.  I was really hoping it wasn't that dumb.

Thank you, you rock!

[jbrzozoski]

Yep, Windows SES build/debug work again, also.  This needs to make it's way upstream quickly.

[AndreasF]

Hi.

Thanks for the input, I have forwarded this.

Best regards,

Andreas

[rkguy]

appears as if it has been fixed in latest master commit using purepath

https://docs.python.org/3/library/pathlib.html

    kconfig_file = os.path.join(module, kconfig_setting or 'zephyr/Kconfig')
    if os.path.isfile(kconfig_file) and kconfig_out is not None:
        kconfig_out.write('osource "{}"\n\n'
                          .format(PurePath(
                              os.path.abspath(kconfig_file)).as_posix()))