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 21:11:41 +0100 [thread overview]
Message-ID: <20081027211141.0935d9c0@surf> (raw)
In-Reply-To: <87zlkphoas.fsf@macbook.be.48ers.dk>
Le Mon, 27 Oct 2008 19:43:07 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> Do you have any ideas about how to solve this in a nicer way?
Not really. Maybe the Config.in read by kconfig could be generated by
the Makefile system. Either completely from the Makefiles, or from
Config.in.tmp files, parsed and modified to contain the dependencies.
However, there are some packages with optional dependencies, like in
matchbox:
ifeq ($(strip $(BR2_PACKAGE_X11R7_LIBXCOMPOSITE)),y)
ifeq ($(strip $(BR2_PACKAGE_X11R7_LIBXPM)),y)
MATCHBOX_WM_OPTS+=--enable-composite
MATCHBOX_WM_DEPS+=xlib_libXcomposite
MATCHBOX_WM_DEPS+=xlib_libXpm
MATCHBOX_LIB_DEPS+=xlib_libXpm
endif
endif
I'm not sure how to handle that kind of case.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-10-27 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 16:56 [Buildroot] Synchronisation of dependencies between Config.in and .mk files ? Thomas Petazzoni
2008-10-27 17:32 ` Roberto A. Foglietta
2008-10-27 18:43 ` Peter Korsgaard
2008-10-27 20:11 ` Thomas Petazzoni [this message]
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=20081027211141.0935d9c0@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