From: Grant Edwards <grante@visi.com>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] CDL question
Date: Tue, 01 Aug 2006 02:37:00 -0000 [thread overview]
Message-ID: <20060801023656.GA28316@grante.dsl.visi.com> (raw)
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
next reply other threads:[~2006-08-01 2:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 2:37 Grant Edwards [this message]
2006-08-01 16:27 ` Andrew Lunn
2006-08-01 18:08 ` [ECOS] " Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2009-06-06 14:01 [ECOS] " Sergei Gavrikov
2001-08-23 10:25 Trenton D. Adams
2001-08-23 10:39 ` Bart Veer
2000-04-12 8:46 Grant Edwards
2000-04-12 9:02 ` Bart Veer
2000-04-12 9:15 ` Grant Edwards
2000-04-12 9:36 ` Bart Veer
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=20060801023656.GA28316@grante.dsl.visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).