Next Steps for Ninja on Windows

[robertapplin]

Describe the outcome that is desired. These are the next steps for using ninja to develop Mantid on windows.

• [x] 1. Try to use ccache as seen on Linux. We might need to add ccache to the conda recipes, and possibly do some more configuration steps to make sure its set up properly. #34494
• [x] 2. Try using CLion on windows to compile and debug with Ninja. Make sure the developer instructions are up to date so that CLion becomes an across-the-board tool on each OS. https://github.com/mantidproject/mantid/pull/34500/
• [ ] 3. Add a pipeline which will just do the build steps for Mantid using MSVC. We do not want it to run the tests as we only want to check that everything gets compiled as expected! (We do want to build the tests - anything that can be compiled we want to build) Talk to Tom and Sarah about this
• [ ] 4. Switch our current windows cloud machines to compile with Ninja. This will hopefully give us a speed boost and it makes sense our primary supported windows compiler is used in the majority of our CI.

[robertapplin]

Progress when trying to use ccache on windows:

1. I activated my environment and did conda install -c conda-forge ccache
2. I made sure the following was executed for windows in the CommonSetup.cmake

   option(USE_CCACHE "Use ccache to cache object artifacts if available" ON)
   if(USE_CCACHE)
   find_program(CCACHE_FOUND ccache)
   if(CCACHE_FOUND)
   set_property(GLOBAL PROPERTY RULE_LAUNCH_COMPILE ccache)
   set_property(GLOBAL PROPERTY RULE_LAUNCH_LINK ccache)
   endif()
   endif()

3. I generated a new build with cmake --preset=win-ninja -B=../build && cd ../build && ninja
4. I looked in /path/to/AppData/Roaming/ccache. There appears to be some caching going on