From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Selecting one of many packages only
Date: Mon, 25 Aug 2014 12:08:20 +0200 [thread overview]
Message-ID: <540d4cac2ea9afb81eef4390ecb56ac2@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <53FB07DD.6070307@dirk-schnitzler.de>
Hei hei,
Am 2014-08-25 11:54, schrieb Dirk Schnitzler:
> Is there a way to exclude the rest of a list of packages if one of
> them was selected (like e.g. radiobuttons)?
In general: yes. In Kconfig this could look like this (copied from one
of our custom .in files):
choice
prompt "CMAKE BUILD TYPE"
default ISBUILD_TYPE_EMPTY
help
This sets CMAKE_BUILD_TYPE for all ifak system libraries and
applications. Default is 'RelWithDebInfo' which is the default
of ptxdist. Possible values are Debug, Release, RelWithDebInfo
and MinSizeRel.
config ISBUILD_TYPE_EMPTY
bool
prompt "empty"
config ISBUILD_TYPE_DEBUG
bool
prompt "Debug"
config ISBUILD_TYPE_RELEASE
bool
prompt "Release"
config ISBUILD_TYPE_RELWITHDEBINFO
bool
prompt "RelWithDebInfo"
config ISBUILD_TYPE_MINSIZEREL
bool
prompt "MinSizeRel"
endchoice
> It's about different configurations that I want to maintain in my
> system, only one can be active.
> The selected config is basically a link "/etc/my-prj/active" which
> points to either
> "/etc/my-prj/config-1" or "/etc/my-prj/config-2", etc, etc.
> Is there a way to do so with the ".in" files or am I going the wrong way?
It's a little more complicated in the .make rule though, you have to
test each bool separatly.
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
prev parent reply other threads:[~2014-08-25 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 9:54 Dirk Schnitzler
2014-08-25 10:08 ` Alexander Dahl [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=540d4cac2ea9afb81eef4390ecb56ac2@idefix.lespocky.dyndns.org \
--to=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