Examine the use of tailored virtual environments per project subdirectory #149
Description
Currently, we are using a single virtual venv required to be activated prior to cmake invocation.
This creates conflicts with tools that use variations of Python deps and are not necessarily linked.
This is especially prevalent in the runtime/samples/ subdirectory where iree-turbine is required and in the WIP SNAX cluster integration where the target toolchain (snax-mlir based on xdsl) is using pixi.
Examine if it's possible for each venv to be setup by the corresponding CMakeLists.txt and what would that mean on rebuilds and test execution.
Resources:
- Creating venv from CMake here