From: "Luqman Munawar" <haqim1@gmx.de>
To: ecos-discuss@ecos.sourceware.org
Cc: Gary Thomas <gary@mlbassoc.com>
Subject: Re: [ECOS] difference between active / enabled components?
Date: Fri, 15 Feb 2008 15:20:00 -0000 [thread overview]
Message-ID: <20080215152005.189850@gmx.net> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2008-02-15 15:20 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
2008-02-15 15:20 ` Luqman Munawar [this message]
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=20080215152005.189850@gmx.net \
--to=haqim1@gmx.de \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
/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).