This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: difference between active / enabled components?
- From: "Luqman Munawar" <haqim1 at gmx dot de>
- To: ecos-discuss at ecos dot sourceware dot org
- Cc: Gary Thomas <gary at mlbassoc dot com>
- Date: Fri, 15 Feb 2008 16:20:05 +0100
- Subject: Re: [ECOS] difference between active / enabled components?
- References: <20080215144826.206640@gmx.net> <47B5A742.9010701@mlbassoc.com>
hi, Thanks for your reply.
> It's all about inferences;
> active - the option is "turned on", i.e. will affect the build
Well, my observation is that when an option is just active and not enabled then it does not affect the build. Since there is no define created in headers, no extra code can be activated.
> enabled - the prerequisites for the item are active, so this item
> can be activated if desired
>
I concur. You can enable an option only when it is activated.
Regards,
Luqman Munawar
--
Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games!
http://games.entertainment.web.de/de/entertainment/games/free
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss