mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Moritz Warning <m.warning@meteocontrol.de>
To: Alexander Dahl <post@lespocky.de>,
	"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] custom menu
Date: Tue, 9 Jun 2015 15:29:48 +0200	[thread overview]
Message-ID: <5576EA4C.7010402@meteocontrol.de> (raw)
In-Reply-To: <d5c466efe8c8ab0c5490537b70075390@localhost>

Thanks, that did it.

On 06/09/2015 02:24 PM, Alexander Dahl wrote:
> Hei hei,
>
> Am 2015-06-09 13:01, schrieb Moritz Warning:
>> I tried to create a custom menu entry and created a file rules/Kconfig:
>
> You don't need to.
>
>> There are also a few rules/*.in files containing "##
>> SECTION=project_specific" on top. But no change in the
>> menu can be seen.
>
> Without changes in some Kconfig this should lead to showing those
> packages at the top of the menuconfig.
>
>> Any ideas?
>> (do not laugh, it is ptxdist-2012.03.0)
>
> We already told you in IRC this is not recommended. ;-) But I think the
> menu mechanism was not touched and should work with your BSP, too.
>
> Besides: I have one rule in my BSP, containing "project_specific" in the
> first line and it looks somewhat like the following:
>
>
> ## SECTION=project_specific
>
> menuconfig MY_DEVICE
>      bool
>      select FOO
>      select BAR
>      prompt "my Device                     "
>      default y
>
> if MY_DEVICE
>
>      choice
>          prompt "baz"
>
>          config OPT_THIS
>              bool
>              prompt "this     "
>
>          config OPT_THAT
>              bool
>              prompt "that        "
>      endchoice
>
>      menu "First submenu                "
>          source "generated/firstsubmenu.in"
>      endmenu
>
>      source "generated/anotherthing.in"
>
> endif
>
> # vim: ft=kconfig noet tw=72
>
>
> This firstsubmenu.in however is not there as a file but I have other
> rules starting with '## SECTION=firstsubmenu' which are put there
> automatically.
>
> This way the menuconfig is not filled with all my packages but with one
> additional submenu where I can put under all my other stuff.
>
> HTH & Greets
> 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

      reply	other threads:[~2015-06-09 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 11:01 Moritz Warning
2015-06-09 11:49 ` Moritz Warning
2015-06-09 12:24 ` Alexander Dahl
2015-06-09 13:29   ` Moritz Warning [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=5576EA4C.7010402@meteocontrol.de \
    --to=m.warning@meteocontrol.de \
    --cc=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