From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] converting busybox config for ptxdist
Date: Fri, 30 Mar 2012 09:55:07 +0200 [thread overview]
Message-ID: <30541aaf2fdbbff00370fd0237cbcdd2@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <4F74D7B2.9030406@lespocky.de>
Am 2012-03-29 23:44, schrieb Alexander Dahl:
> As far as I remember from last week, ptxdist .in file just sources the
> Kconfig from busybox. Busybox uses the same config system, it's just
> assimilated. ;-)
Because of curiosity I just had another look on this. Speaking of
ptxdist 2012.03.0, rules/busybox.in contains this shortly before end of
file:
73 source "config/busybox/Config.in"
This file is distributed with ptxdist itself. Busybox source contains a
very similar file, so I did a diff against both, which starts like this:
--- platform-at91sam9g20ncl/build-target/busybox-1.18.5/Config.in
2011-06-12 17:41:51.00000000 0 +0200
+++ /home/adahl/src/ptxdist/config/busybox/Config.in 2011-09-07
12:08:37.000000000 +0200
@@ -3,9 +3,9 @@
# see scripts/kbuild/config-language.txt.
#
-mainmenu "BusyBox Configuration"
+# mainmenu "BusyBox Configuration"
-config HAVE_DOT_CONFIG
+config BUSYBOX_HAVE_DOT_CONFIG
bool
default y
@@ -13,7 +13,7 @@
menu "General Configuration"
-config DESKTOP
+config BUSYBOX_DESKTOP
bool "Enable options for full-blown desktop systems"
default y
help
This goes on for a while, each config option is prefixed with BUSYBOX_,
I guess some script or editor magic did this. In the end there are
additionally sourced files also from busybox source tree, which are part
of the ptxdist source tree, too. Same magic here. If you look at the
last changes to busybox package in Git, you'll see these files are
changed for each busybox version bump:
http://git.pengutronix.de/?p=ptxdist.git;a=history;f=config/busybox;hb=HEAD
However I couldn't find any script in ptxdist source for doing the
conversion of files from one to the other source tree, maybe the
commiter has one?!
Hope this is a little more clear than my guessing from memory
yesterday. O:-)
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-03-30 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 15:27 Alexander Stein
2012-03-29 21:44 ` Alexander Dahl
2012-03-30 7:55 ` Alexander Dahl [this message]
2012-03-30 8:57 ` Alexander Dahl
2012-04-02 10:28 ` Alexander Stein
2012-04-02 10:49 ` Marc Kleine-Budde
2012-04-02 11:36 ` Alexander Stein
2012-04-02 11:37 ` Marc Kleine-Budde
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=30541aaf2fdbbff00370fd0237cbcdd2@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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