LGHT0103 error when -b path has a space and guidance in LG0117 is followed. #4361
Comments
|
You have to quote paths with spaces. The error message is saying that it found a quote inside the path, which is illegal. The reason is that the command line is escaped, so
|
|
Thank you for the clarification. I realize now that I should have posted this to the user forum first. When I enclose the -b path (which includes a space) with quotes, and also add a backslash in front of the trailing quote to 'escape' it, then it works as you suggest. So I guess this is a non-issue. But conceptually (and when viewing the log message, even on success) this remains confusing because the "path' I provided to -b did not have any embedded quotes, only one set of enclosing quotes, and the solution is to escape only the trialing quote. Strange, but it works for me. Thanks for the help!
|
|
|
|
When the path used with the -b option is in the from:
-b "\Server\Drive\parentFolder\Folder With_Space"
LGHT0117 is displayed with the advice that the message "C:\Program' cannot contain a quote. Quotes are often accidentally introduced when trying to refer to a directory path with spaces in it, such as "C:\Out Directory". The correct representation for that path is: "C:\Out Directory"
When the path used with the -b option is in the from:
-b \Server\Drive\parentFolder\Folder With_Space\
LGHT0103 is displayed "LGHT0103: The system cannot find the file 'With_Space' with type 'Source'."
Background: I am using the -b option to provide the root of a source tree, and then in the MSI project specifying the remainder of the path to the file in the Source attribute. This seems to result in faster builds in comparison to using preprocessor statements. But I did not find a way to deal with a space in the path.
The text was updated successfully, but these errors were encountered: