Document the project policy on mixing build systems. [skip ci] #6603
Conversation
| or that they are built as Meson subprojects under the main | ||
| project. There are several projects that would like to mix build | ||
| systems, that is, build dependencies in the same build directory in | ||
| the same build directory by having one build system call the other. |
There was a problem hiding this comment.
"in the same build directory in the same build directory" (duplicated)
| work), and even if it works today there are no guarantees that it will | ||
| keep working in any future version. | ||
|
|
||
| ## The definition of "buils system mixing" |
jpakkane
force-pushed
the
mixbuildsystems
branch
from
6e74772 to
f5e85d8
Compare
|
I'm not sure if this means cargo module as proposed in #2617 would be accepted or not. |
I would interpret this as meaning "go ahead and merge it", because it meets all these requirements. |
| project. There are several projects that would like to mix build | ||
| systems, that is, build dependencies in the same build directory as | ||
| the other build system by having one build system call the other. The | ||
| build diectories do not necessarily need to be inside each other, but |
| tl/dr version is that while we do provide some functionality for this | ||
| use case, it only works for simple cases. Anything more complex can | ||
| not be made reliable and trying to do that would burden Meson | ||
| developers with an effectively infinite maintenance burder. Thus these |
| build diectories do not necessarily need to be inside each other, but | ||
| that is the common case. | ||
|
|
||
| This page lists the Meson project's stance on mixing build system. The |
|
The point of this PR was to make it possible to merge things like #2617. It does not mean that they will be automatically and blindly merged, though. They must be reviewed as usual and in addition every piece of functionality (mostly modules) that falls under this rule must start its documentation by referring to this guide (like the CMake module does in this commit). |
jpakkane
force-pushed
the
mixbuildsystems
branch
from
f5e85d8 to
4decf0e
Compare
No description provided.