mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Tobias Schmidl <T.Schmidl@erhardt-leimer.com>
To: ptxdist <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Scripting of Kconfig options
Date: Wed, 8 Apr 2015 07:57:18 +0200	[thread overview]
Message-ID: <OFB7A189C2.CD94D92D-ONC1257E21.00207B64-C1257E21.0020B64E@erhardt-leimer.com> (raw)
In-Reply-To: <20150402161738.GH20251@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 963 bytes --]

Hello Michael,

-----ptxdist-bounces@pengutronix.de schrieb: -----
>> 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.

thanks, will try!

Best regards,

    Tobias

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 11118 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2015-04-08  5:57 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
2015-04-08  5:57 ` Tobias Schmidl [this message]

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=OFB7A189C2.CD94D92D-ONC1257E21.00207B64-C1257E21.0020B64E@erhardt-leimer.com \
    --to=t.schmidl@erhardt-leimer.com \
    --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