Skip to content
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

Fixes build errors on Windows when project path contains spaces #196

Merged
merged 1 commit into from
May 23, 2018

Conversation

tincann
Copy link
Contributor

@tincann tincann commented May 21, 2018

Fixes #191

The problem seemed to be that %~dp0 was used in the batch scripts without proper quoting.

@dnfclas
Copy link

dnfclas commented May 21, 2018

CLA assistant check
All CLA requirements met.

@Ivanidzo4ka
Copy link
Contributor

@dotnet-bot test Windows_NT Release

@Ivanidzo4ka Ivanidzo4ka requested a review from eerhardt May 21, 2018 21:23
Copy link
Member

@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @tincann for the help, it's much appreciated.

I just have a couple minor comments.

@@ -37,7 +36,8 @@ if exist %_VSWHERE% (
if not exist "%_VSCOMNTOOLS%" set _VSCOMNTOOLS=%VS140COMNTOOLS%
if not exist "%_VSCOMNTOOLS%" goto :MissingVersion

set VSCMD_START_DIR="%__currentScriptDir%"

set VSCMD_START_DIR=%__currentScriptDir%
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this set different than the 2 below? For example, the two below have the format set "name=%__currentScriptDir%" where this one doesn't have the surrounding double-quotes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. I've added the quotes again (also around the variable for consistency).

@@ -44,7 +44,7 @@

<!-- Run script that invokes Cmake to create VS files, and then calls msbuild to compile them -->
<Message Text="$(MSBuildProjectDirectory)\build.cmd $(BuildArgs)" Importance="High"/>
<Exec Command="$(MSBuildProjectDirectory)\build.cmd $(BuildArgs)" />
<Exec Command="&quot;$(MSBuildProjectDirectory)\build.cmd&quot; $(BuildArgs)" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears the unix build has the same issue. Would it be possible to fix the Unix build as well?

Copy link
Contributor Author

@tincann tincann May 22, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Certainly, I have some time in the end of the week. Shall I put this in a new pull request, so the Windows fix can already be put to use now?

Copy link
Member

@eerhardt eerhardt May 22, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is totally fine with me to create another PR for that.

@tincann tincann changed the title Fixes build errors when project path contains spaces Fixes build errors on Windows when project path contains spaces May 22, 2018
Copy link
Contributor

@Ivanidzo4ka Ivanidzo4ka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@Ivanidzo4ka Ivanidzo4ka merged commit 76393f4 into dotnet:master May 23, 2018
eerhardt pushed a commit to eerhardt/machinelearning that referenced this pull request Jul 27, 2018
@ghost ghost locked as resolved and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants