I wanna try Meson! I will fork and study this.

An indirect benefit of this is that Meson supports Xcode and MSVC.

I wanna try Meson! I will fork and study this.

An indirect benefit of this is that Meson supports Xcode and MSVC.

Awesome! thx @AndersonTorres :D

Meson would be lovely :)

I am planning to study the current system first. It has some low level interactions like building bios files from 32-bit assembly...

Hello.
Seems, migration to meson build system stalled. Any chances to adopt CMake? I can perform that migration. I can also update current autotools project to recent versions - this relatively easy task and can be done quicklier than migration.

Oh man, I need to take this seriously!
I vote for a new autotools first.
Cmake is too bloated, I am not a big fan of it. Meson is way easier.

Hello. Seems, migration to meson build system stalled. Any chances to adopt CMake? I can perform that migration. I can also update current autotools project to recent versions - this relatively easy task and can be done quicklier than migration.

@winterheart 💯
Moving to CMake would be an amazing addition to the project. Not to mention it would easily to integrate to other projects already using cmake. I don't think moving bochs to cmake would be hard, all necessary features already are built-in (like pre-building scripts, even packaging and more)

Cmake is too bloated, I am not a big fan of it. Meson is way easier.

CMake is less trivial but more advanced than Meson (in my opinion and experience - not trying to start a war 🙂)

I'd be more than happy to also contribute if you decide to go that route.

Not continuing the war, in my experience as a Nixpkgs contributor, cmake is harder to isolate.

In Nixpkgs we regularly patch cmake scripts that try to download things during build.
Meson also allows downloads, but

1. In Meson you can block downloads via cmdline args;
2. In Meson you can provide beforehand the files that would be downloaded; it just checks the hash;
3. In cmake there is no way to do the things above: cmake forces the download, ignoring the files you provided;
4. The only way to avoid the things in the above bullet is just by heavy patching the scripts;
5. It is not easy to convince people that "hey, can you at least add this custom code in order to honor previously downloaded packages?".

For the programmer it maybe makes few to no difference; however for a package manager, it can be really annoying.