mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: kbuild dependencies and layout
Date: Sun, 24 Oct 2004 23:43:52 +0000	[thread overview]
Message-ID: <1098661432l.6459l.0l@werewolf.able.es> (raw)

Hi all...

I'm trying to make a small modification to the Kconfig files, but I can't
get the menu layout match what I want.

Say I want this logic:

menu "A support"
  config A_1
    tristate "A-1"
  config A_2
    tristate "A-2"
  config A_GENERIC_FEATURE_1
    bool "AF1"
    depends on A_1 || A_2
  config A_GENERIC_FEATURE_2
    bool "AF2"
    depends on A_1 || A_2
endmenu

A_GENERIC_FEATURE_1 is valid for both submodels. Logic is right, but
gconfig insists on putting AF1 as a subentry of A_2, instead of hanging
it in the menu. I would like:

  A support
   \- A-1
   \- A-2
   \- AF1 (visible only when A-1 or A-2 are selected)
   \- AF2 (visible only when A-1 or A-2 are selected)

but I get

  A support
   \- A-1
   \- A-2
      \- AF1 (visible only when A-1 or A-2 are selected)
      \- AF2 (visible only when A-1 or A-2 are selected)

(ie, both optional features haged on A-2)

What am I doing wrong ? Is there any way to defeat the auto-layout
based on depedencies of kbuild ?

TIA

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.1 (Community) for i586
Linux 2.6.9-jam1 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #1



             reply	other threads:[~2004-10-24 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-24 23:43 J.A. Magallon [this message]
2004-10-25 14:09 ` Roman Zippel
2004-10-25 23:32   ` J.A. Magallon
2004-10-27  0:19     ` Roman Zippel

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=1098661432l.6459l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®