cmake: Add more advanced subproject configuration options #7231
Conversation
mensinda
added
subprojects/wraps
dependency:cmake
This comment has been minimized.
This comment has been minimized.
This is done with the new cmake subprojects options object that is similar to the already exisiting configuration data object. It is consumed by the new `options` kwarg of the cmake.subproject function.
|
|
||
| ### `cmake options` object | ||
|
|
||
| This object is returned by the `subproject_options()` function and consumed by |
There was a problem hiding this comment.
This should be "method", not "function".
There was a problem hiding this comment.
Just to clarify, are all root functions of a module methods? Up until now, I have only used the term "method" for functions/methods of an object and not a module.
If "method" should also for module functions/methods I will change it for all occoruences in the CMake module docs.
There was a problem hiding this comment.
I don't know if "method" is the correct term here or even if an actual proper term even exists. The difference I had in mind is that "functions" look like this:
freestading_function()
whereas methods are always invoked via something else like this:
some.bound_function()
That is clearly the case when some is an object but it's less clear when it is a "module" or something similar. Anyhow, since this would require changing all the docs, let's go with this for now.
There was a problem hiding this comment.
OK, sure. Does this PR get a dev freeze exception then :)
This is done with the new cmake subprojects options object that is similar to the already existing configuration data object. It is consumed by the new
optionskwarg of the cmake.subproject function.