[ECOS] CDL question

[ECOS] CDL question

[Grant Edwards]

I've read through the CDL sections of the component developer's
guide, but I can't figure out what the command is to set a data
flavored option to an expression involving it's default value
or it's current value.

Assume I've got an ecos.ecc file that I generated via an
"ecosconfig new whatever" command.  Now I want to change the
value of CYGBLD_GLOBAL_CFLAGS (which has its default value) to
add "-DFooBar".  This needs to be done in a shell script so
that I can automate the entire build process.  Usually when I
need to make automated changes to ecos.ecc I create a .cdl file
and import it like this:

   cat >.tmp$$.cdl <<EOF
   cdl_option CYGBLD_BUILD_REDBOOT_WITH_GDB {user_value 0}
   cdl_option CYGBLD_BUILD_REDBOOT_WITH_ZLIB {user_value 0}
   EOF
   ecosconfig import .tmp$$.cdl

However, I can't figure out what the TCL expression is for "the
current value of option CYG_WHATEVER".  I thought perhaps something like
   
   option CYGBLD_GLOBAL_CFLAGS {user_value "$CYGBLD_GLOBAL_CFLAGS -DFooBar"}

But that doesn't work.  I'm sure it's something obvious, but
I've never been able to grok TCL no matter how hard I try...

-- 
Grant Edwards
grante@visi.com



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] CDL question

[Andrew Lunn]

On Mon, Jul 31, 2006 at 09:36:58PM -0500, Grant Edwards wrote:
> I've read through the CDL sections of the component developer's
> guide, but I can't figure out what the command is to set a data
> flavored option to an expression involving it's default value
> or it's current value.
> 
> Assume I've got an ecos.ecc file that I generated via an
> "ecosconfig new whatever" command.  Now I want to change the
> value of CYGBLD_GLOBAL_CFLAGS (which has its default value) to
> add "-DFooBar".  This needs to be done in a shell script so
> that I can automate the entire build process.  Usually when I
> need to make automated changes to ecos.ecc I create a .cdl file
> and import it like this:
> 
>    cat >.tmp$$.cdl <<EOF
>    cdl_option CYGBLD_BUILD_REDBOOT_WITH_GDB {user_value 0}
>    cdl_option CYGBLD_BUILD_REDBOOT_WITH_ZLIB {user_value 0}
>    EOF
>    ecosconfig import .tmp$$.cdl
> 
> However, I can't figure out what the TCL expression is for "the
> current value of option CYG_WHATEVER".  I thought perhaps something like
>    
>    option CYGBLD_GLOBAL_CFLAGS {user_value "$CYGBLD_GLOBAL_CFLAGS -DFooBar"}
> 
> But that doesn't work.  I'm sure it's something obvious, but
> I've never been able to grok TCL no matter how hard I try...

This method will not work. tcl has no access to CDL
variables. $CYGBLD_GLOBAL_CFLAGS means nothing to tcl.

You could use the cdl_option CYGPKG_KERNEL_CFLAGS_REMOVE,
CYGPKG_KERNEL_LDFLAGS_ADD etc to add FooBar to specific packages, in
this example the kernel. 

Another idea would be something like adding a custom package with CDL
something like:

cdl_option CYGBLD_DIDDLE_THE_FLAGS {
     flavor data
     default_value ""
     requires { is_substr(CYGBLD_GLOBAL_CFLAGS, CYGBLD_DIDDLE_THE_FLAGS) }
}

Then you can set CYGBLD_DIDDLE_THE_FLAGS from your import file and the
inference engine will do the rest.

          Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: CDL question

[Grant Edwards]

In gmane.os.ecos.general, you wrote:

>> I've read through the CDL sections of the component developer's
>> guide, but I can't figure out what the command is to set a data
>> flavored option to an expression involving it's default value
>> or it's current value.

>> However, I can't figure out what the TCL expression is for "the
>> current value of option CYG_WHATEVER".  I thought perhaps something like
>>    
>>    option CYGBLD_GLOBAL_CFLAGS {user_value "$CYGBLD_GLOBAL_CFLAGS -DFooBar"}
>> 
>> But that doesn't work.  I'm sure it's something obvious, but
>> I've never been able to grok TCL no matter how hard I try...
>
> This method will not work. tcl has no access to CDL
> variables. $CYGBLD_GLOBAL_CFLAGS means nothing to tcl.

I've decided I'm attacking this from the wrong direction.  What
I really ought to do is just add a separate CDL option and
change the C code to check for that option instead of for
"FooBar".

-- 
Grant Edwards                   grante             Yow!  Four thousand
                                  at               different MAGNATES, MOGULS
                               visi.com            & NABOBS are romping in my
                                                   gothic solarium!!

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] CDL question

[Sergei Gavrikov]

Hello

I'm trying to join a few HALs for almost the same boards in a single HAL
package. The boards have the same CPU and RAM, but they differ by the
FLASH parts and LAN controllers. I had an idea to select one target name
and then to select the kind of the hardware using the CDL validators:
is_substr, is_active.

It works fine, but, now I want evaluate `legal_values' list, and I found
that I cannot manage it like `default_value' or `calculated' things.  Is
it possible evaluate legal_values list? First, I think that I will can
manage the issue using quotes instead brackets, but that did not work
with the list. Well, it is possible to solve a puzzle using a few CDL
options, but, a question is, Is it possible to solve the puzzle inside
one component using no extra options and just using the expression for
`legal_values' list?

What I try to do using CDL expressions

if {board == A} {
	default_value A
	legal_values {A B C}
} else if {board == B} {
	default_value X
	legal_values {X Y Z}
}

and using in two-lines coding I could get only, for example,

	default_value B
	legal_values {A B C X Y Z}

Thanks for any comments on it.

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: CDL question

[John Dallaway]

Hi Sergei

Sergei Gavrikov wrote:

> What I try to do using CDL expressions
> 
> if {board == A} {
> 	default_value A
> 	legal_values {A B C}
> } else if {board == B} {
> 	default_value X
> 	legal_values {X Y Z}
> }
> 
> and using in two-lines coding I could get only, for example,
> 
> 	default_value B
> 	legal_values {A B C X Y Z}
> 
> Thanks for any comments on it.

The following should work, but there may be a more elegant approach:

  default_value { (board == "A") ? "A" : "X" }
  legal_values {
    ((board == "A") ? "A" : "")
    ((board == "A") ? "B" : "")
    ((board == "A") ? "C" : "")
    ((board == "B") ? "X" : "")
    ((board == "B") ? "Y" : "")
    ((board == "B") ? "Z" : "")
  }

John Dallaway

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: CDL question

[Sergei Gavrikov]

John Dallaway wrote:
 
> The following should work, but there may be a more elegant approach:
> 
>   default_value { (board == "A") ? "A" : "X" }
>   legal_values {
>     ((board == "A") ? "A" : "")
>     ((board == "A") ? "B" : "")
>     ((board == "A") ? "C" : "")
>     ((board == "B") ? "X" : "")
>     ((board == "B") ? "Y" : "")
>     ((board == "B") ? "Z" : "")
>   }

Hi,

Thank you. I'm sorry, I was being AFK. Hm, your pseudo-CDL code is like
mine. Perhaps, my mixture was too comprecated and I missed the brackets
in the expression, true speaking in my check were many many is_substr()
concatenations, I will try it again.

I will going to try some stupid? thing. I wonder, if I will create some
fake tree (~ecos repository):

.
|-- ecos.db
|-- baz
|   `-- current
|       `-- cdl
|           `-- baz.cdl
`-- templates
    `-- bar
        `-- current.cdl

and my ecos.db will be contain only single fake target `foo' with
CYGPKG_BAR. Will I be able to validate CDL-pseudo code just using
`ecosconfig' as

ECOS_REPOSITORY=`pwd` ecosconfig new foo bar

Will ecosconfig complain? Well, I'll try it.

Thank you,

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: CDL question

[Sergei Gavrikov]

On Sat, Jun 06, 2009 at 08:47:41PM +0300, Sergei Gavrikov wrote:
> I will going to try some stupid? thing. I wonder, if I will create some
> fake tree (~ecos repository):

[snip]

> Will ecosconfig complain? Well, I'll try it.

It works if set up the sandbox properly. And what did I expect :-) ? So,
it's easy to setup sandbox repository with one or few study-packages,
and learn CDL insides, use `ecosconfig' as CDL lint, and even observe
sandbox tree in CT. All toy-options after `ecosconfig tree' a pupil will
find in include/pkgconf/foo.h. What a nice thing this eCos!

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss