Running SanityCheck in Windows

[zephyrbot]

Reported by Inaky Perez-Gonzalez:

A developer working under the Windows environment shall be able to run SanityCheck under said Windows environment to verify basic operation of his/her modifications.

SanityCheck has been developed and it is mainly operated under Linux; a comprehensive porting effort has to be undergone and the following points were identified as possibly initial contention:

• Python package dependencies issues
• CR/LF issues
• Qemu glitches
• makefile jobserver (minor)

(Imported from Jira ZEP-1174)

[carlescufi]

Additional info:

scripts/sanitycheck does not run on Windows.

In order to be able to have CI on Windows machines we would need at the very least:

• The script should be able to build only (no QEMU) on Windows
• We should have a way to provide multiple toolchains to sanitycheck without an SDK

[carlescufi]

Current state of things: There's a class in sanitycheck called MakeGenerator that invokes make in its execute method. We need to replace this with something else that is not make in order to get rid of this dependency on Windows.

[SebastianBoe]

"The script should be able to build only (no QEMU) on Windows"

NB: The script itself has a flag for specifying --build-only.

" -b, --build-only Only build the code, do not execute any of it in QEMU"

[SebastianBoe]

"Current state of things: There's a class in sanitycheck called MakeGenerator that invokes make in its execute method. We need to replace this with something else that is not make in order to get rid of this dependency on Windows."

Note that this is what: "makefile jobserver (minor)" was trying to say in the initial Jira issue.

Essentially, sanitycheck is using Make as a jobserver, we need to replace it with some portable piece of technology to ensure we are running an appropriate amount of threads at any given time.