[libcxx] [libcxxabi] [libunwind] [CMake] Handle multiple flags in ADDITIONAL_COMPILE_FLAGS properly (PR #112703)

2024-10-18 Thread Stephanos Ioannidis via cfe-commits
stephanosio wrote: @ldionne Thanks for clarifying. I will close this since `{LIBCXX,LIBCXXABI,LIBUNWIND}_ADDITIONAL_COMPILE_FLAGS` was never meant to take space-separated compile flags. https://github.com/llvm/llvm-project/pull/112703 ___ cfe-commits

[libcxx] [libcxxabi] [libunwind] [CMake] Handle multiple flags in ADDITIONAL_COMPILE_FLAGS properly (PR #112703)

2024-10-18 Thread Stephanos Ioannidis via cfe-commits
https://github.com/stephanosio closed https://github.com/llvm/llvm-project/pull/112703 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[libcxx] [libcxxabi] [libunwind] [CMake] Handle multiple flags in ADDITIONAL_COMPILE_FLAGS properly (PR #112703)

2024-10-17 Thread Stephanos Ioannidis via cfe-commits
https://github.com/stephanosio created https://github.com/llvm/llvm-project/pull/112703 When multiple space-separated compile flags are specified in an `ADDITIONAL_COMPILE_FLAGS` cache string, the resulting flags are enclosed by double quotes because `ADDITIONAL_COMPILE_FLAGS` is a string (i.e