This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: difference between active / enabled components?
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Luqman Munawar <haqim1 at gmx dot de>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Fri, 15 Feb 2008 07:52:50 -0700
- Subject: Re: [ECOS] difference between active / enabled components?
- References: <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