Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Getting Kconfig menu right
Date: Thu, 28 Jul 2011 08:48:50 +0200	[thread overview]
Message-ID: <20110728084850.180f50a3@skate> (raw)
In-Reply-To: <CAMkyJgDML5mip30tPA9962uOjHnzAWFVWTKRr8RZei3LG6W1ew@mail.gmail.com>

Le Thu, 28 Jul 2011 00:30:22 +0300,
Avishay Orpaz <avishorp@gmail.com> a ?crit :

> I'm trying to add python-fuse to buildroot. I have the makefile
> working, but there is only one little problem left. I would like the
> option for python-fuse to show up as a sub-item of libfuse, only when
> libfuse is checked. It should be similar, for example, to lua - when
> selected, some relevant sub-options appear as sub-items in the
> xconfig menu. I looked very closely on the lua Config.in, but found
> nothing that tells Kconfig to show all the options as a sub-items.
> How can I do this?

If python-fuse is a separate package of libfuse, then there is no way
python-fuse can be a suboption of libfuse. You can only make
python-fuse not visible when libfuse is disabled and make it visible
when libfuse is visible. You'd need a package/python-fuse/Config.in
file that looks like this :

config BR2_PACKAGE_PYTHON_FUSE
	bool "python-fuse"
	depends on BR2_PACKAGE_LIBFUSE
	depends on BR2_PACKAGE_PYTHON
	help
	  This is python-fuse blabla.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2011-07-28  6:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 21:30 [Buildroot] Getting Kconfig menu right Avishay Orpaz
2011-07-27 21:46 ` ANDY KENNEDY
2011-07-27 21:50   ` Avishay Orpaz
2011-07-28  6:48 ` Thomas Petazzoni [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=20110728084850.180f50a3@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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