From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Makefile: don't rely on linux-tools being sorted alphabetically
Date: Sun, 9 Jul 2017 14:41:24 +0200 [thread overview]
Message-ID: <20170709124124.GC3196@scaer> (raw)
In-Reply-To: <855c5444-80f0-491b-5d70-aef7cd13b110@mind.be>
Arnout, All,
On 2017-07-09 13:10 +0200, Arnout Vandecappelle spake thusly:
> On 09-07-17 10:13, Yann E. MORIN wrote:
> > Markus, All,
> >
> > On 2017-07-05 10:19 -0700, Markus Mayer spake thusly:
> > [--SNIP--]
> >> That said, and while I am a complete buildroot newbie, I do like the
> >> suggestion of creating sub-directories for the tools and including the
> >> makefiles from linux-tools.mk rather than relying on alphabetical
> >> sorting.
> >
> > To be sure we're on the same line: one single sub-directory with all tools
> > in there, not one sub-dir per tool.
>
> Really? One sub-dir per tool would be more in-line with how we handle normal
> packages.
Well, I would find it a bit over-blown to have many sub-dirs with a
single file (the .mk) in each.
Unless you also expected that the big Config.in file be split too?
I would argue against, because its fate is already a bit special: it is
not sourced from package/Config.in but from linux/Config.in. and I would
prefer we avoid a bit more complexity...
Regards,
Yann E. MORIN.
> Regards,
> Arnout
>
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-07-09 12:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 23:54 [Buildroot] [PATCH 0/2] Add linux-tool-tmon Markus Mayer
2017-07-04 23:54 ` [Buildroot] [PATCH 1/2] Makefile: don't rely on linux-tools being sorted alphabetically Markus Mayer
2017-07-05 7:25 ` Yann E. MORIN
2017-07-05 7:38 ` Yann E. MORIN
2017-07-05 8:15 ` Arnout Vandecappelle
2017-07-05 8:09 ` Arnout Vandecappelle
2017-07-05 8:18 ` Arnout Vandecappelle
[not found] ` <CAGt4E5ueb6x_S4ff=dAeK-x9JnO1SmhnUGz+Q3XKUtj6s24L_Q@mail.gmail.com>
2017-07-05 17:19 ` Markus Mayer
2017-07-08 21:16 ` Arnout Vandecappelle
2017-07-09 0:00 ` Markus Mayer
2017-07-09 8:13 ` Yann E. MORIN
2017-07-09 11:10 ` Arnout Vandecappelle
2017-07-09 12:41 ` Yann E. MORIN [this message]
2017-07-10 3:49 ` Markus Mayer
2017-07-13 20:16 ` Markus Mayer
2017-07-13 21:45 ` Yann E. MORIN
2017-07-13 23:59 ` Markus Mayer
2017-07-16 15:08 ` Yann E. MORIN
2017-07-17 7:37 ` Thomas Petazzoni
2017-07-17 15:36 ` Yann E. MORIN
2017-07-17 17:32 ` Markus Mayer
2017-07-04 23:54 ` [Buildroot] [PATCH 2/2] package/linux-tools: add tmon Markus Mayer
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=20170709124124.GC3196@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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