This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: CDL Inferred Value
- From: Jay Foster <jay at systech dot com>
- To: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 20 May 2010 17:16:45 -0700
- Subject: Re: [ECOS] CDL Inferred Value
- References: <4B9ACE82.4040805@jifvik.org> <4BF5CE5F.9070709@systech.com>
I think I figured out the issue. The component had a requires
dependency on another option that was disabled in my template, but then
re-enabled from an imported .ecm file. Since the component in question
is never explicitly enabled (or disabled), it was left in the disabled
state.
On 5/20/2010 5:05 PM, Jay Foster wrote:
I have a CDL file with a component defined. It has flavor 'bool' and
a 'default_value' of 1. I do not configure this option in any of my
templates or .ecm files, so expect to get the default value
(1=enabled). However, I end up with it disabled. The .ecc file shows
that the user_value is 1 (commented out), the default_value is 1
(commented out) and the inferred value is 0 with the value_source =
inferred. How does this happen? What are the rules for inferred values?
Jay
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss