From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH v4 00/10] group llvm projects and bump to version 15.0.3
Date: Thu, 20 Jul 2023 23:06:38 +0200 [thread overview]
Message-ID: <20230720230638.5eba8786@windsurf> (raw)
In-Reply-To: <pan$86c9$5fa777aa$e5fc1042$fce28aaf@ID-313208.user.individual.net>
Hello Bernd,
On Thu, 20 Jul 2023 21:00:54 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> quoting the user manual:
> http://buildroot.uclibc.org/downloads/manual/
> manual.html#_package_directory
>
> "New subdirectories are discouraged, however."
Correct, with one exception: when a reasonable number of packages share
some common variables, especially the version variable. It's the case
for qt5, but it's also the case for those llvm-project packages, in
which case we tend to accept having a subdirectory.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-20 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230615134315.494330-1-sebastian.weyer__49449.699586124$1686836642$gmane$org@smile.fr>
2023-07-20 19:00 ` [Buildroot] [PATCH v4 00/10] group llvm projects and bump to version 15.0.3 Bernd Kuhls
2023-07-20 21:06 ` Thomas Petazzoni via buildroot [this message]
2023-06-15 13:43 Sebastian Weyer
2023-07-18 0:01 ` Adam Duskett
2023-07-20 21:05 ` Thomas Petazzoni via buildroot
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=20230720230638.5eba8786@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.