1 |
It maybe worth considering switching the default generator in the |
2 |
cmake-utils.eclass from the default of emake to ninja. |
3 |
|
4 |
- : ${CMAKE_MAKEFILE_GENERATOR:=emake} |
5 |
+ : ${CMAKE_MAKEFILE_GENERATOR:=ninja} |
6 |
|
7 |
For those with cmake ebuilds you can test this out now via |
8 |
|
9 |
CMAKE_MAKEFILE_GENERATOR="ninja" |
10 |
inherit cmake-utils |
11 |
|
12 |
Working with both cmake and meson. It seems the real performance of |
13 |
meson comes from ninja. I am a bit more a fan of cmake than meson for |
14 |
cpack, generation of deb, rpm, and binary tarball, in addition to |
15 |
sources. That can be done with meson but not as elegantly at this time. |
16 |
|
17 |
ninja is noticeably faster than make. I haven't seen any cases yet where |
18 |
cmake autotools works, and ninja does not. They seem pretty equal, so |
19 |
should be safe. Of course could use testing first. |
20 |
|
21 |
Again something to consider. Myself I am avoiding autotools anywhere I |
22 |
can, mostly because of the slow configure and also slow make. Anytime I |
23 |
use cmake, I am using ninja generator. |
24 |
|
25 |
-- |
26 |
William L. Thomson Jr. |