Windows support

[Pennycook]

Feature/behavior summary

CBI is developed on Linux and only tested on Linux, but it would be nice to support Windows as well.

Request attributes

• Would this be a refactor of existing code?
• Does this proposal require new package dependencies?
• Would this change break backwards compatibility?

Related issues

• Rename files that rely on case-sensitive paths #190

Solution description

• Ensure that the Git repository can be cloned correctly on Windows.
• Run the unit tests and see if anything fails.
• Update this issue with a list of all test failures.
• Address test failures.
• Enable regular testing on Windows via GitHub Actions.

Additional notes

No response

[laserkelvin]

I have never developed compiled code on Windows - do we have a sense of what is feasible on Windows in terms of the general tooling?

I know CMake is supported, but AFAIK Clang can't be used directly by itself for example (as in you need some extra tooling). Just wanted to see what CBI functionality might be reduced, if any.

[Pennycook]

I have never developed compiled code on Windows - do we have a sense of what is feasible on Windows in terms of the general tooling?

I've never developed code on Windows either. No idea.

I know CMake is supported, but AFAIK Clang can't be used directly by itself for example (as in you need some extra tooling). Just wanted to see what CBI functionality might be reduced, if any.

I think as long as our dependencies are available, things should work.

But I really don't know! That's why the TODO list in this issue starts with "see what's broken" 😆. If it's not feasible, we'll just close the issue and move on.