From: Gary Thomas <gary@mlbassoc.com>
To: Luqman Munawar <haqim1@gmx.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] difference between active / enabled components?
Date: Fri, 15 Feb 2008 14:53:00 -0000 [thread overview]
Message-ID: <47B5A742.9010701@mlbassoc.com> (raw)
In-Reply-To: <20080215144826.206640@gmx.net>
Luqman Munawar wrote:
> hello,
>
> I have a general question regarding the difference between an active and enabled option/components.
>
> I have checked that there is a define for every option that is both active and enabled otherwise no define is created in the headers.
>
> So what is the use of having both of them? Is it just for cosmetic reasons in configtools?
It's all about inferences;
active - the option is "turned on", i.e. will affect the build
enabled - the prerequisites for the item are active, so this item
can be activated if desired
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-02-15 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 14:48 Luqman Munawar
2008-02-15 14:53 ` Gary Thomas [this message]
2008-02-15 15:20 ` Luqman Munawar
2008-02-15 15:37 ` Andrew Lunn
2008-02-18 11:23 ` [ECOS] enabling/disabling options Luqman Munawar
2008-02-18 11:31 ` Gary Thomas
2008-02-18 13:05 ` Luqman Munawar
2008-02-18 13:21 ` Bart Veer
2008-02-18 13:10 ` [ECOS] difference between active / enabled components? Bart Veer
2008-02-18 15:58 ` Luqman Munawar
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=47B5A742.9010701@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=haqim1@gmx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).