Displaying 2 results from an estimated 2 matches for "backslases".
Did you mean:
backslashes
2014 Mar 22
2
[LLVMdev] compiler-rt CMake build ignores CMAKE_CXX_FLAGS
...missing-field-initializers\ -pedantic\
-Wno-long-long\ -Wcovered-switch-default\ -Wnon-virtual-dtor\
-std=c++11\ -fcolor-diagnostics\ -ffunction-sections\ -fdata-sections\
-Wall\ -std=c++11 -m64 -c -o gtest-all.cc.x86_64.o
/home/llvmbb/clang/llvm/utils/unittest/googletest/src/gtest-all.cc
Note the backslases in the command.
Could maintainers of the compiler-rt CMake scripts help me with this?
Dmitri
--
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/
2014 Mar 24
2
[LLVMdev] compiler-rt CMake build ignores CMAKE_CXX_FLAGS
...long-long\ -Wcovered-switch-default\ -Wnon-virtual-dtor\
>> -std=c++11\ -fcolor-diagnostics\ -ffunction-sections\ -fdata-sections\
>> -Wall\ -std=c++11 -m64 -c -o gtest-all.cc.x86_64.o
>> /home/llvmbb/clang/llvm/utils/unittest/googletest/src/gtest-all.cc
>>
>> Note the backslases in the command.
>>
>
> Yep, because CMAKE_CXX_FLAGS is a string, and its contents is automatically
> escaped when we use it in COMMAND in CMake rules. I guess we'll have to
> manually
> turn CMAKE_CXX_FLAGS into a CMake semicolon-separated list.
>
>
>>
>>...