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
Complete quoting for parameters of some CMake commands. #1104
Complete quoting for parameters of some CMake commands. #1104
Conversation
…e commands A wiki article pointed out that whitespace will only be preserved for parameters in CMake commands if passed strings will be appropriately quoted or escaped. http://cmake.org/Wiki/CMake/Language_Syntax#CMake_splits_arguments_unless_you_use_quotation_marks_or_escapes. Quoting was added so that more places should also handle file names correctly which contain space characters or semicolons eventually. Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
…_of_some_CMake_commands Complete quoting for parameters of some CMake commands.
I'm impressed by the amount of work you put into this! Thanks a lot! |
This patch causes compilation of one of the examples to fail. See here: http://hermione.cct.lsu.edu/builders/hpx_gcc46_x8664_boost152_debug/builds/306/steps/build_core/logs/stdio. Would you be able to fix this? |
I admit that I did not test all possible software combinations for my update suggestion. I imagine that I can not fix this unexpected build failure alone.
It seems that the text "slurm-test-HPX-storage" is referenced at one place. (Do you know a bit more about this component?) |
The issue above seems to be fixed now, but there is another one: http://hermione.cct.lsu.edu/builders/hpx_docs/builds/172/steps/build_docs/logs/stdio which looks like is related to the quoting changes. |
Please tell me how the issue was fixed around the "Slurm script generator". Next issue:
|
Frankly, I have no idea how the issue above was solved :-P. The only change I made was to avoid that the target was built always (f75896a). The buildbot is just a automated tool executing the build scripts, I doubt it's involved (it worked before). The variable |
Do we need to clarify the passing of directory names with quotation marks in more detail for two build failures? |
I'm not sure I understand what you mean. Could you elaborate, please? |
Did you notice that the error messages from the two build logs mentioned directories with quotation marks in the names? |
Did you report build failures that are two permanent open issues at the moment? |
I find it interesting here that you renamed an involved variable. |
Does a specific display from your build bot indicate that my update suggestion did not damage your software generation process more than I hoped to make it a bit safer? |
I'm sorry that I inserted a quotation mark somehow at the wrong place. |
|
|
A wiki article pointed out that whitespace will only be preserved for parameters in CMake commands if passed strings will be appropriately quoted or escaped.
Quoting can be added so that more places should also handle file names correctly which contain space characters or semicolons eventually.