mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Moritz Warning <m.warning@meteocontrol.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] custom menu
Date: Tue, 9 Jun 2015 13:49:38 +0200	[thread overview]
Message-ID: <5576D2D2.2030308@meteocontrol.de> (raw)
In-Reply-To: <5576C780.8090409@meteocontrol.de>

Ok,

the Kconfig files needs to be in $BSP/, not $BSP/rules.

But I cannot use the template:
$cp /usr/local/lib/ptxdist-2012.03.0/rules/templates/kconfig/Kconfig .
$ ./ptxdist menuconfig
config/Kconfig:6: invalid statement

ptxdist: ' menuconfig' returned with an error


But it work when I copy the global Kconfig and add a submenu there:
cp /usr/local/lib/ptxdist-2012.03.0/rules/Kconfig .
$ ./ptxdist menuconfig
<works>

Any ideas on how to use the template? Copying over and then modifying 
the global Kconfig is not the way to go...


On 06/09/2015 01:01 PM, Moritz Warning wrote:
> Hi,
>
> I tried to create a custom menu entry and created a file rules/Kconfig:
>
> source "config/Kconfig"
>
> comment "--------- Project Specific Menu -------------"
>
> menu "Project Specific Menu               "
> source "generated/project_specific.in"
> endmenu
>
>
> There are also a few rules/*.in files containing "##
> SECTION=project_specific" on top. But no change in the
> menu can be seen.
> It looks like rules/Kconfig is completely ignored.
>
> Any ideas?
> (do not laugh, it is ptxdist-2012.03.0)
>
> regards and cookies,
> mwarning
>

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-06-09 11:49 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 [this message]
2015-06-09 12:24 ` Alexander Dahl
2015-06-09 13:29   ` Moritz Warning

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=5576D2D2.2030308@meteocontrol.de \
    --to=m.warning@meteocontrol.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