public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: cmake + ninja vs autotools
Date: Sun, 19 Nov 2017 16:49:51 +0000 (UTC)	[thread overview]
Message-ID: <ouscnf$i3l$1@blaine.gmane.org> (raw)
In-Reply-To: assp.04953791fa.20171117210323.5dd6d824@wlt.obsidian-studios.com

William L. Thomson Jr. <wlt-ml@o-sinc.com> wrote:
>
> case ${CMAKE_MAKEFILE_GENERATOR} in
>         emake)
>                 DEPEND="sys-devel/make"
>                 ;;
>         ninja)
>                 DEPEND="dev-util/ninja"
>                 ;;

This is broken: Static metadata like DEPEND must not depend
on dynamic data like environment variables which are supposed
to change at emerge time.

> Only 2 thus far does not sound like most things would have issues.

In fact, almost nothing has issues. I am using
CMAKE_MAKEFILE_GENERATOR=ninja in my make.conf
since years, and the total list of packages which had
ever failed here (out of currently ~1500 installed)
is this:

dev-util/cmake
kde-apps/kate
kde-apps/gwenview
media-libs/avidemux-core
media-libs/avidemux-plugins
media-video/avidemux
media-video/kaffeine
media-video/kmplayer
net-vpn/kvpnc
sci-mathematics/reduce

This list might appear long, but note that

1. */avidemux* is essentially only 1 package
2. net-vpn/kvpnc is ancient and masked
3. sci-mathematics/reduce is ancient and masked

and moreover, perhaps some other entries of this list are even
obsolete (I do not have installed KDE 5, so I cannot try quickly;
when I had added the packages to the list, KDE 4 was rather new...)

> Ninja is most of the speed of meson less configure time savings

++
For eix, the main motivation to support meson as an
alternative build system was to be able to use ninja...



  reply	other threads:[~2017-11-19 16:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16  3:27 [gentoo-dev] cmake + ninja vs autotools William L. Thomson Jr.
2017-11-16 13:28 ` Brian Evans
2017-11-16 13:44   ` Christoph Junghans
2017-11-16 16:17     ` Christoph Junghans
2017-11-16 16:40       ` William L. Thomson Jr.
2017-11-17 23:35 ` [gentoo-dev] " Michael Palimaka
2017-11-18  1:52   ` Francesco Riosa
2017-11-18  2:03     ` William L. Thomson Jr.
2017-11-19 16:49       ` Martin Vaeth [this message]
2017-11-19 18:00         ` William L. Thomson Jr.
2017-11-19 19:20           ` Michael Orlitzky
2017-11-19 19:10         ` Georg Rudoy
2017-11-22 10:17           ` Martin Vaeth
2017-11-23 16:36             ` Peter Stuge
2017-11-24 22:46               ` William L. Thomson Jr.
2017-11-25  0:20                 ` Peter Stuge
2017-11-25  0:51                   ` William L. Thomson Jr.
2017-11-25  1:35                     ` Peter Stuge
2017-11-25  1:37                     ` Peter Stuge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ouscnf$i3l$1@blaine.gmane.org' \
    --to=martin@mvath.de \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox