mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Scripting of Kconfig options
Date: Thu, 2 Apr 2015 18:17:38 +0200	[thread overview]
Message-ID: <20150402161738.GH20251@pengutronix.de> (raw)
In-Reply-To: <OFE19BB167.E98407D4-ONC1257E15.006AF3BF-C1257E15.006B12B3@erhardt-leimer.com>

Hi,

On Fri, Mar 27, 2015 at 08:29:31PM +0100, Tobias Schmidl wrote:
> I'm trying to automate a ptxdist build via Jenkins. Therefore, I need to
> select a (known) PTXDist menuconfig option via shell script, i.e. "ptxdist
> menuconfig" is not really an option.
> 
> Right now the whole thing is done via sed, but I'm wondering if there is
> a more pratical way of choosing an option fron an option group&#8230;

By 'option group' you mean a 'choice' right? I don't think, that there is
some special tool. I'd use sed and then 'fix' the ptxconfig with
"ptxdist oldconfig < /dev/null". For a choice that would be:
1. Remove all alternatives
2. Append the option you want at the end of the file
3. Run oldconfig

Kconfig will then keep the option you added and adds the others with 'is
not set'.

This keeps the sed magic simple and still produces a valid ptxconfig.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-04-02 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 19:29 Tobias Schmidl
2015-04-02 16:17 ` Michael Olbrich [this message]
2015-04-08  5:57 ` Tobias Schmidl

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=20150402161738.GH20251@pengutronix.de \
    --to=m.olbrich@pengutronix.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