soundshaped
commented
6 years ago overview of my solve (seems to be a path issue)
This is somewhat asked and answered by myself but I'm not convinced there isn't some kind of error occurring regarding how the choco install wasn't finding the dependency it installed itself.
I added C:\msys64\usr\bin to my System Variables PATH and running cabal install tidal in an admin powershell worked. As a clarification: in my previous post the second time I tried to do only the cabal part of the install was in a new admin powershell window because I figured the path might need to update. This might have not been the proper way in powershell - in bash I'm used to either exec $shell/source .bashrc/ or just opening a new window or tab to update environment variables. Maybe I should have exited the first window.
From checking my User Variables PATH it seems like I have two installations of MSYS64 as C:\tools\msys64 was already in the PATH after being installed this morning during the choco install tidal cycles first attempt (I imagine because I had not added the already installed MSYS64 bin to my path). Aside from my user error it does read as odd that while chocolatey was getting the dependencies installed and even installed MSYS64 that it didn't know where to find the dependency it had just installed.
Now in atom when trying to run the simple d1 $ sound "bd sn" I get the following error which I was also getting after the first install attempt:
'gchi' is not recognized as an internal or external command, operable program or batch file.' The same behavior followed in the powershell. Interestingly the command for the specific version of ghci worked ieghci-8.4.3.exe` was a recognized command.
Upon restarting atom after updating path and exiting all powershell windows and then opening a new powershell window tidal cycles works.
Why couldn't cabal in the choco install properly locate a dependency installed by the choco script
In a sense this is resolved but I'm hesitant to say that because my mildly informed opinion is that the chocolatey install should have worked originally and it seems like something broke down since it couldn't call on dependencies it had just installed to continue and finish the install without error. This computer isn't clean in the sense that it is a fresh install however it's only a couple months old, a secondary computer, with regard to tidal cycles it is clean - I hadn't install it nor supercollider.
Regardless I obviously don't have the expertise on the issue at this point so I'll stop typiing for now.
morikoh
yaxu
Hey - so I'm new to developing with windows so I'm very likely to forget to include some relevant information please just let me know.
Basically I'm running windows 10 and already had some things installed for package managing/development on windows but I wouldn't say my environment is organized and I imagine digital hygiene is likely the issue.
I have installed:
Error during install
So from looking at the output (I've saved the full output but here is the chunk where I noticed the error). Basically when
cabal install tidalis install it seems like most things install fine but a few packages don't make it.Here is the tail of the error
From what I'm gathering from this the install breaks down with the configure step failure of
network-2.7.0.2because it requires MinGW+MSYS which I have previously installed. How doescaballocate or look for MinGW+MSYS - is this a path related error?In googling around these errors I found a github post from the author of this repo which addresses what I think is an identical error though not identical issue if that makes sense. The issue with the post in question seems to be the installation method of haskell. I'm under the impression that the
choco installinstalls haskell and in powershell I can enter the haskell console fine though can't doimport Sound.Tidal.OscStream. I can try downloading the full haskell from the website but it doesn't make sense to me that the haskell install via chocolatey wouldn't work while the other installer would work.This the relevant info I can think to include right now. I'm happy to supply more if needed. Thanks!
here is the powershell output truncated to just the cabal part