[plan] This conflict only occurs due to tests, so it's a real shame it limits us in our production code.
I think the correct thing to do is isolate the CMake tests somehow. It is already a bit odd the way we build and run a CMake project from within a pytest test case. But that's obviously not a small fix.
It'd be great if we could decouple the test runtime from the generation runtime, so we don't have this conflict in the first place, as it's not a traitgen conflict per-se.
Following on from this fun, @feltech noted that:
_Originally posted by @feltech in https://github.com/OpenAssetIO/OpenAssetIO-TraitGen/pull/31#discussion_r1267018457_
It'd be great if we could decouple the test runtime from the generation runtime, so we don't have this conflict in the first place, as it's not a traitgen conflict per-se.