This PR changes the way erbb setup install the MSYS2 Ming64 tools we use to build the simulator and use cairo to produce graphics (making the panel in different formats).
It does so by directly copying the relevant file rather than relying on the MSYS2 package manager. In practice, our users can have different configurations and it becomes difficult to make sure eurorack-blocks is directly installed. To circumvent this:
We install the packages we need in the eurorack-blocks build-system to provide isolation
We changed the build-system to ensure we select our versions of the tools
To ensure we select properly our tools, we manipulate the PATH, but do this from within python. This ensures:
We don't polute the global environment of the user
We make sure that the order of directories in the PATH do not have any impact on eurorack-blocks tool selection.
Removing the dependency on msys2 also removes one manual installation, and make the eurorack-blocks installation more lean.
Finally, the method we use is similar to the one chosen for Daisy.
This PR changes the way
erbb setupinstall the MSYS2 Ming64 tools we use to build the simulator and use cairo to produce graphics (making the panel in different formats).It does so by directly copying the relevant file rather than relying on the MSYS2 package manager. In practice, our users can have different configurations and it becomes difficult to make sure eurorack-blocks is directly installed. To circumvent this:
To ensure we select properly our tools, we manipulate the
PATH, but do this from within python. This ensures:PATHdo not have any impact on eurorack-blocks tool selection.Removing the dependency on msys2 also removes one manual installation, and make the eurorack-blocks installation more lean.
Finally, the method we use is similar to the one chosen for Daisy.