public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Usage of dev-utils/ninja in ebuilds
Date: Sat, 25 May 2013 19:53:28 -0600	[thread overview]
Message-ID: <20130525195328.7b09215e@caribou.gateway.2wire.net> (raw)
In-Reply-To: 51A1077E.1030607@gentoo.org

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

On Sat, 25 May 2013 14:48:30 -0400
Mike Gilbert <floppym@gentoo.org> wrote:

> I'm wondering if we should create a more global function for calling
> ninja in a consistent way. Maybe we should introduce a NINJAOPTS
> variable for users to set in make.conf. Should we create a new eclass
> for this, or just stick it in eutils?

Is NINJAOPTS a variable recognized by ninja or something that would be Gentoo
specific?  It'd be nice if you could parse out what you need from MAKEOPTS
instead, but I have no strong feelings.

If there's only two users in the tree right now I don't think an eclass is
warranted.


-- 
Ryan Hill                        psn: dirtyepic_sk
   gcc-porting/toolchain/wxwidgets @ gentoo.org

47C3 6D62 4864 0E49 8E9E  7F92 ED38 BD49 957A 8463

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2013-05-26  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 18:48 [gentoo-dev] Usage of dev-utils/ninja in ebuilds Mike Gilbert
2013-05-25 19:17 ` Tom Wijsman
2013-05-25 19:45   ` Mike Gilbert
2013-05-26  3:01     ` "Paweł Hajdan, Jr."
2013-05-25 21:09   ` Luca Barbato
2013-05-26  1:53 ` Ryan Hill [this message]
2013-05-26  1:55   ` [gentoo-dev] " Mike Gilbert
2013-05-26  2:00   ` Alex Xu
2013-05-26  4:23     ` Ryan Hill

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=20130525195328.7b09215e@caribou.gateway.2wire.net \
    --to=dirtyepic@gentoo.org \
    --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