-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails if there are spaces in path name #691
Comments
Hey @Zajn: I just noticed this issue. Is still a problem for you? |
On Windows 10, I would expect that running |
It's not the same error, but I still cannot build immediately after cloning. I pulled the latest, and ran
Running
|
Try running |
Ah -- I'm betting the problem is with spaces in the path name. |
Hah, looks like you're right! If I have time in the next few days, I could try and create a PR to address that. |
I've encountered several issues trying to build omnisharp on Windows 10 x64, but now have gotten stuck. The furthest I've gotten into the
build.cake
script isRestore
, which fails as such:Here was the list of the issues I encountered:
I ran the
build.ps1
install script in PowerShell, and get an error very similar to #484 where the script complains that thecake
executable is not available.However, upon further investigation with
-verbose
, it appears that there is something wonky with theNuGet
command to fetch the tools. This is the error I see:I got past this by running:
but then the
build.cake
script complains aboutdotnet
not being available in the.dotnet
directory.Symlinking the system
dotnet
to this directory seems to fix that. I did try modifying thebuild.json
to use the Systemdotnet
instead, but then script will complain that it can't find thedotnet
executable for some reason.Once I symlinked
dotnet
under.dotnet
, I got to the error in theRestore
task.Any idea where I might be going wrong? I think I have all the correct dependencies installed. I don't have a lot of experience with development on Windows, so I might missing something easy.
The text was updated successfully, but these errors were encountered: