Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] external, how to achieve our needs?
Date: Wed, 26 Feb 2020 16:14:21 +0100	[thread overview]
Message-ID: <875zft8joy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200226132916.5umjrlej5to4shtl@M43218.corp.atmel.com> (Ludovic Desroches's message of "Wed, 26 Feb 2020 14:29:16 +0100")

>>>>> "Ludovic" == Ludovic Desroches <ludovic.desroches@microchip.com> writes:

 > Hi Mircea,
 > On Wed, Feb 26, 2020 at 12:11:36PM +0000, Mircea GLIGA wrote:
 >> Hi Ludovic,
 >> 
 >> I also have this kind of problems when implementing our external,
 >> sometimes is useful to 'override' or append to a recipe (Yocto
 >> style).
 >> 
 >> * I ended up "duplicating" recipes in our layer, e.g. bd-tcpdump
 >> in order to build the package differently

 > From the top of my head, I tried this and I got an error when duplicating
 > the recipes in the external. Did you use other tricks?

Buildrot uses a global namespace, so you have to rename the package (and
the makefile/kconfig symbols) for it to work.

It naturally only works for packages without any reverse dependencies as
those packages doesn't know about your custom 'foo' package.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2020-02-26 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 15:01 [Buildroot] external, how to achieve our needs? Ludovic Desroches
2020-02-26  5:36 ` Baruch Siach
2020-02-26 13:20   ` Ludovic Desroches
2020-02-26 12:11 ` Mircea GLIGA
2020-02-26 13:29   ` Ludovic Desroches
2020-02-26 15:14     ` Peter Korsgaard [this message]
2020-02-26 21:59       ` Vadim Kochan
2020-02-26 13:30 ` Mircea GLIGA

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=875zft8joy.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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