Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Synchronisation of dependencies between Config.in and .mk files ?
Date: Mon, 27 Oct 2008 17:56:45 +0100	[thread overview]
Message-ID: <20081027175645.7e7cb096@surf> (raw)

Hi,

Currently, there are two complementary ways of expressing dependencies
between packages:

 * Through the select BR2_FOOBAR statements in the Config.in files ;

 * Through the FOOBAR_DEPS variable in the package makefiles.

The second one is absolutely necessary, as it makes sure that packages
are built in the proper order. The first one allows packages Makefiles
to adapt their configuration depending on the existing dependencies
(i.e if tslib is available, then enable support for touchscreens, etc.).

However, there are great chances for these two lists of dependencies
for each package to become unsynchronized.

What's the policy about this ? What are the current techniques to keep
them synchronized ?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2008-10-27 16:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 16:56 Thomas Petazzoni [this message]
2008-10-27 17:32 ` [Buildroot] Synchronisation of dependencies between Config.in and .mk files ? Roberto A. Foglietta
2008-10-27 18:43 ` Peter Korsgaard
2008-10-27 20:11   ` Thomas Petazzoni
2008-10-27 20:32     ` Peter Korsgaard
2008-10-27 20:46       ` Roberto A. Foglietta
2008-10-27 21:47     ` Markus Heidelberg
2008-10-27 22:33       ` Roberto A. Foglietta
2008-10-27 23:26         ` Markus Heidelberg
2008-10-28  0:07         ` Grant Likely
2008-10-28  7:32         ` Peter Korsgaard

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=20081027175645.7e7cb096@surf \
    --to=thomas.petazzoni@free-electrons.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