Fix Compiler Not found in the windows CI when building with ninja

Context

Ninja is an alternative build backend to make that is quite faster. Introduced by @cguillon in this MR we would like to add it as default build backend for the project.

Error

However when trying to use it in the ci on windows jobs, it results in "compiler not found error". I haven't been able to this error on my machine, hinting that the issue comes from the image buildtools ? Maybe we need to the compiler path as cmake argument.

Error in the ci when calling cmake .. -G Ninja ${other_args} https://gitlab.eclipse.org/eclipse/aidge/aidge_core/-/jobs/394281

changed the description

mentioned in merge request !154 (merged)

As mentionned in MR !154 (merged) the issue for your report is:

• one should add any tools used for build in build-requires (or setup_requires in setup.py), this is because on modern python installations, the setup is run in isolation, and thus any package not mentionned in setup_requires will be missing.

Then also as discussed in the MR, in fact I discovered that using ninja instead of the default build backend on Windows (which is MSVC when installed and not "make" as on linuxes) would need more work, indeed:

• with the default MSVC backend, when installed cmake generate a MSVC project and thus use the MSVC SDK backend which finds itself the compiler etc...
• with ninja or make as windows backend the user would have to install and configure the compiler to be in the path etc...
  • we could require to use some compiler such as clang or configure to find ourself msvc if present, but as it is not a priority on windows to develop, I guess we should forget this now and let the default MSVC install for windows

Hence to close the issue, if you want to try:

• 1st: add in build requires/setup_requires "ninja"
• 2nd: then you should see something like cmake finding ninja and starting to configure but probably fail because it does not find a compiler...

added Bug 🐛 CI ⚡ labels

added OSWindows label