Replies: 3 comments
-
I don't think that's necessary. There are examples that use the function, such as this one. I would prefer to keep things minimal as a baseline and put interesting things in the wiki as an example. This might also be better as a discussion rather than an issue I think. |
Beta Was this translation helpful? Give feedback.
-
Does this example still work for multi-configs scenarios? For example this line looks outdated: https://github.com/friendlyanon/generate-opaque-structs/blob/218bd01cbdaf038d6ddf89bc4f9715ce4de7a782/CMakeLists.txt#L45 |
Beta Was this translation helpful? Give feedback.
-
There is nothing outdated there. I don't understand. |
Beta Was this translation helpful? Give feedback.
-
Occasionally, I have to use CMake variables inside my C/C++ files. A canonical way to get access to these variables is to parse the file via
configure_file()
; however, I find it non-trivial to insert this into the existing template. What about showcasing this by, for example, returningCMAKE_PROJECT_NAME
instead of hard coding the name here. Another common use case is to return the project version as a string.Beta Was this translation helpful? Give feedback.
All reactions