-
Notifications
You must be signed in to change notification settings - Fork 57
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
CMAKE_C?_FLAGS are not lists but strings #191
Comments
Care to send a pull-request? |
Really, for such a small & trivial change? |
mjp41
added a commit
to mjp41/mimalloc-bench
that referenced
this issue
Aug 8, 2023
Fixes CMAKE_C?_FLAGS are not lists but strings daanx#191
Merged
I had the files open, so pushed a PR. #192 |
mjp41
added a commit
that referenced
this issue
Aug 9, 2023
Fixes CMAKE_C?_FLAGS are not lists but strings #191
derSteFfi
pushed a commit
to derSteFfi/mimalloc-bench
that referenced
this issue
Sep 7, 2023
Fixes CMAKE_C?_FLAGS are not lists but strings daanx#191
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mimalloc-bench/bench/CMakeLists.txt
Line 44 in 6e4bbc7
CMake lists are semicolon-separated affairs so appending flags to
CMAKE_C?_FLAGS
withlist(APPEND CMAKE_C?_FLAGS "-foo -bar")
will introduce a semicolon in the final compiler invocation if those flags aren't empty. Which can be the case if the user calls CMake withCFLAGS
and/orCXXFLAGS
in the environment.The proper way to append compiler flags is a string append operation, e.g.
The text was updated successfully, but these errors were encountered: