When working on a large project which happens to have multiple build systems, (C, C++) in this case, they may use multiple build systems -- for different platforms, or for historic reasons.With the popularity of meta-build systems, there is the opportunity to use a single build system which can generate files for different platforms.The disadvantages for using multiple build-systems seem rather obvious...maintenance overhead.higher barrier of entry for developers,(needing some experience in multiple build systems)more files to navigate in the source repository.Ignoring the effort it may take to do the initial migration, are there any advantages to keeping multiple build-systems in use? (when there is the opportunity to use only one?)Said differently, if someone comes into a project and suggests to use a single cross platform build system, are there any reasonable arguments against this?Since it was requested I be more specific, the projects I have in mind are large C/C++ code bases, using a mix of automake, MSVC-project-files, SCons & in one case CMake (which is an example of a meta-build system).
Any advantage to using multiple build systems?
build system