My McCode (McStas/McXtrace) checkout in (...) is available to you via an MCP plugin.

The codes are built using CMake - and we are gradually moving to mainly focusing on conda-forge as distribution channel, the McStas recipe is found here:
https://github.com/conda-forge/mcstas-suite-feedstock

I would like to integrate this new library from Greg Tucker which is placed in an independent repo https://github.com/mcdotstar/mcstas-chopper-lib. I would like an automated solution that works at release / config / build time rather than a static import. 

The chopper-lib comes with both 'lib' code (.c/.h snippets) that should end up in the users McStas resource dir 'share', components that should end up in the users McStas resource 'contrib' dir and instruments  should end up in independent folders under the users McStas resource 'examples/Tests_optics' dir.

Please initially take a look at the CMake code in the McStas checkout and investigate 1) if we require a new enough CMake for using FetchContent and 2) how you would propose implementing the wanted mechanism to automatically fetch the mcstas-chopper-lib for distribution / installation