Skip to content

Commit 2993e07

Browse files
ENH: Add warning that quoting CMAKE_ARGS can cause errors
* Add warning after ${CMAKE_ARGS} is first introduced that quoting this variable in recipes can lead to build errors as it is a space separated list of options. - c.f. https://conda-forge.zulipchat.com/#narrow/channel/457337-general/topic/.E2.9C.94.20Validation.20C.2FFortran.20compatibility.20with.20CMAKE_ARGS/with/524918138 Co-authored-by: Isuru Fernando <[email protected]>
1 parent 57bdfbc commit 2993e07

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/maintainer/knowledge_base.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,14 @@ Some optional, but useful CMake options:
8686
- `-DCMAKE_FIND_FRAMEWORK=NEVER` and `-DCMAKE_FIND_APPBUNDLE=NEVER` Prevent CMake from using system-wide macOS packages.
8787
- `${CMAKE_ARGS}` Add variables defined by conda-forge internally. This is required to enable various conda-forge enhancements, like [CUDA builds](#cuda).
8888

89+
:::warning
90+
91+
As `${CMAKE_ARGS}` is a space separated list of options, quoting `${CMAKE_ARGS}`
92+
(`"${CMAKE_ARGS}"`) in recipes can lead to build errors as quoting makes the shell
93+
treat the contents of the variable as a single argument.
94+
95+
:::
96+
8997
Here are some basic commands for you to get started. These are dependent on your source
9098
code layout and aren't intended to be used "as is".
9199

0 commit comments

Comments
 (0)