From: "Marek Olšák" <maraeo@gmail.com>
To: Dylan Baker <dylan@pnwbakers.com>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RFC libdrm 0/2] Replace the build system with meson
Date: Fri, 17 Mar 2017 22:18:10 +0100 [thread overview]
Message-ID: <CAAxE2A7LMHYHR5R4PNXimXSeFHmifcVMdx88UU3ewLYVamCrKQ@mail.gmail.com> (raw)
In-Reply-To: <148972414349.2660.10252539768404130500@localhost.localdomain>
On Fri, Mar 17, 2017 at 5:15 AM, Dylan Baker <dylan@pnwbakers.com> wrote:
> Quoting Marek Olšák (2017-03-16 18:53:59)
>> On Fri, Mar 17, 2017 at 12:11 AM, Dylan Baker <dylan@pnwbakers.com> wrote:
>> > Quoting Marek Olšák (2017-03-16 15:36:26)
>> >> Is there a way not to use ninja with meson, because ninja redirects
>> >> all stderr output from gcc to stdout, which breaks many development
>> >> environments that expect errors in stderr?
>> >>
>> >> I'm basically saying that if ninja can't keep gcc errors in stderr, I
>> >> wouldn't like any project that I might be involved in to require ninja
>> >> for building.
>> >>
>> >> Marek
>> >
>> > There is no way to use another backend on Linux, and meson will not support
>> > Make. Ninja is a big part of the appeal here, since it is faster than make is.
>> > Are there particular tools you know don't work with ninja? It seems like in the
>> > 7+ years since ninja came out that someone would have fixed the tools, or that
>> > some stream redirection could be used to fix the problem, "ninja 1>&2"?
>>
>> I actually read some thread about it and the conclusion seemed to be
>> that ninja developers don't care. I have no other option than to
>> believe that ninja was made for automated build bots, not for
>> development.
>>
>> Some editors expect that errors and only errors go to stderr and all
>> other garbage info goes to stdout. This is something I can't change.
>>
>> Marek
>
> And I found this: https://groups.google.com/forum/#!topic/ninja-build/4syh2jzXWcI
>
> Which leads me to believe that they would be responsive to a patch, the core
> team just doesn't have a use for it. There is in fact a patch already written
> (linked in that thread), that just needs someone to clean it up and propose it
> for merge.
Well, I guess I can use that. It's still not nice to force some people
to use out-of-tree builds of ninja.
Marek
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-17 21:18 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 21:25 [RFC libdrm 0/2] Replace the build system with meson Dylan Baker
2017-03-16 21:25 ` [RFC libdrm 1/2] Port build system to meson Dylan Baker
2017-03-16 21:25 ` [RFC libdrm 2/2] remove autotools build Dylan Baker
2017-03-16 21:32 ` [RFC libdrm 0/2] Replace the build system with meson Ilia Mirkin
2017-03-16 21:57 ` Dylan Baker
2017-03-17 10:05 ` Neil Armstrong
2017-03-16 22:36 ` Marek Olšák
2017-03-16 23:11 ` Dylan Baker
2017-03-17 1:53 ` Marek Olšák
2017-03-17 4:15 ` Dylan Baker
2017-03-17 21:18 ` Marek Olšák [this message]
2017-03-22 17:26 ` Jose Fonseca
2017-03-22 17:50 ` [Mesa-dev] " Marek Olšák
2017-03-16 23:35 ` Emil Velikov
2017-03-17 0:21 ` Dylan Baker
2017-03-17 0:41 ` Emil Velikov
2017-03-17 2:03 ` Jason Ekstrand
2017-03-17 2:28 ` Brian Paul
2017-03-22 17:59 ` Jose Fonseca
2017-03-22 20:57 ` [Mesa-dev] " Dylan Baker
2017-03-22 22:02 ` Rob Clark
2017-03-22 22:15 ` Eric Anholt
2017-03-22 22:33 ` Dylan Baker
2017-03-24 14:03 ` Jose Fonseca
2017-03-24 14:22 ` [Mesa-dev] " Daniel Stone
2017-03-24 15:47 ` Jose Fonseca
2017-03-25 20:15 ` [Mesa-dev] " Rob Clark
2017-03-24 16:23 ` Bas Nieuwenhuizen
2017-03-17 4:12 ` Dylan Baker
2017-03-17 6:02 ` Jonathan Gray
2017-03-20 13:55 ` [Mesa-dev] " Emil Velikov
2017-03-20 18:30 ` Matt Turner
2017-03-20 19:39 ` [Mesa-dev] " Emil Velikov
2017-03-20 21:28 ` Timothy Arceri
2017-03-20 21:38 ` Jason Ekstrand
2017-03-21 5:00 ` Jonathan Gray
2017-03-21 16:00 ` Matt Turner
2017-03-23 12:23 ` Jonathan Gray
2017-03-23 18:31 ` Emil Velikov
2017-03-21 15:57 ` [Mesa-dev] " Matt Turner
2017-03-21 17:16 ` Emil Velikov
2017-03-21 18:06 ` Matt Turner
2017-03-21 18:56 ` [Mesa-dev] " Emil Velikov
2017-03-21 19:08 ` Jason Ekstrand
2017-03-21 19:10 ` [Mesa-dev] " Matt Turner
2017-03-22 17:16 ` Emil Velikov
2017-03-24 20:59 ` Chad Versace
2017-03-24 20:44 ` [Mesa-dev] " Chad Versace
2017-03-28 16:59 ` Emil Velikov
2017-03-28 23:19 ` Timothy Arceri
2017-03-21 5:10 ` Jonathan Gray
2017-03-21 16:11 ` [Mesa-dev] " Matt Turner
2017-03-24 16:58 ` randyf
2017-03-20 19:29 ` Rob Clark
2017-03-21 14:44 ` Jani Nikula
2017-03-21 15:13 ` Grazvydas Ignotas
2017-03-21 15:15 ` Ilia Mirkin
2017-03-21 16:16 ` Dylan Baker
2017-03-21 16:22 ` Dylan Baker
2017-03-22 4:23 ` [Mesa-dev] " Jonathan Gray
2017-03-22 8:24 ` Jani Nikula
2017-03-22 21:05 ` Dylan Baker
2017-03-23 8:13 ` Jani Nikula
2017-03-21 16:50 ` Kai Wasserbäch
2017-03-21 17:34 ` Dylan Baker
2017-03-21 18:36 ` [Mesa-dev] " Kai Wasserbäch
2017-03-21 21:16 ` Dylan Baker
2017-03-22 16:40 ` Alex Deucher
2017-03-22 17:07 ` Rob Clark
2017-03-22 20:10 ` [Mesa-dev] " Dylan Baker
2017-03-22 21:48 ` Rob Clark
2017-03-23 21:56 ` Greg Hackmann
2017-03-23 22:14 ` Colin Cross
2017-03-23 23:56 ` Dylan Baker
2017-03-24 0:03 ` [Mesa-dev] " Colin Cross
2017-03-24 16:54 ` Dylan Baker
2017-03-23 1:18 ` [Mesa-dev] " Jonathan Gray
2017-03-23 1:38 ` Rob Clark
2017-03-24 13:42 ` Jose Fonseca
2017-03-24 17:13 ` Dylan Baker
2017-03-24 17:51 ` Eric Anholt
2017-03-24 18:34 ` [Mesa-dev] " Daniel Stone
2017-03-24 19:10 ` Kristian Høgsberg
2017-03-24 19:44 ` Jose Fonseca
2017-03-24 20:08 ` Kristian Høgsberg
2017-03-24 21:16 ` Jose Fonseca
2017-03-24 21:20 ` Jason Ekstrand
2017-03-24 21:34 ` [Mesa-dev] " Rob Clark
2017-03-25 1:25 ` Dylan Baker
2017-03-24 21:09 ` [Mesa-dev] " Rob Clark
2017-03-23 11:39 ` Emil Velikov
2017-03-23 17:54 ` Dylan Baker
2017-03-25 1:06 ` Kenneth Graunke
2017-03-22 22:30 ` [Mesa-dev] " Eric Anholt
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=CAAxE2A7LMHYHR5R4PNXimXSeFHmifcVMdx88UU3ewLYVamCrKQ@mail.gmail.com \
--to=maraeo@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dylan@pnwbakers.com \
--cc=mesa-dev@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).