-
-
Notifications
You must be signed in to change notification settings - Fork 197
CLI not supporting a project path having a spaces #1455
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
Comments
this fix my issue
the project preparation succeed but the build failed du to the boken path |
I prefer quoting the strings where needed. At any rate, we will fix it. Thank you! |
@vchimev, can we add integration tests with projects with spaces in key places? |
thanks, a lot i want to use the Vmware Shared Folder, and i didnt found how to change the default "Vmware Shared Folder" path, so i stuck for the moment |
you can use your patch for the time being. |
It may contain spaces which fails when passed to the `otool`. Addresses #1455
Wherever possible use `spawn` instead of `exec`. This minifies the chance of something going wrong wherever there are spaces, quotation marks and whatnots in the project's name. Addresses #1455
Wherever possible use `spawn` instead of `exec`. This minifies the chance of something going wrong wherever there are spaces, quotation marks and whatnots in the project's name. Addresses #1455
Wherever possible use `spawn` instead of `exec`. This minifies the chance of something going wrong wherever there are spaces, quotation marks and whatnots in the project's name. Addresses #1455
The
-c otool -Vh /Volumes/VMware Shared Folders/dev/nativescript/gregories/
should be-c otool -Vh /Volumes/VMware\ Shared\ Folders/dev/nativescript/gregories/
The text was updated successfully, but these errors were encountered: