From: Andrew Lunn <andrew@lunn.ch>
To: Mike Arthur <arth2219@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] How to modify CFLAGS within an ECM file?
Date: Wed, 12 Sep 2007 18:02:00 -0000 [thread overview]
Message-ID: <20070912180157.GR3557@lunn.ch> (raw)
In-Reply-To: <2a3305fe0709121012gf922917vc8ab6acb744a6e7a@mail.gmail.com>
On Wed, Sep 12, 2007 at 12:12:36PM -0500, Mike Arthur wrote:
> > Take a look at:
> >
> > http://ecos.sourceware.org/docs-latest/cdl-guide/language.values.html
> >
> > In particular the first example after the table of operators, the
> > example in the section Functions, and the documentation for is_substr()
> >
>
>
> I get this error while trying to import my .ecm file:
> ---------------------------------------------------------------------
> option CYGBLD_GLOBAL_CFLAGS: error
> invalid command name "requires"
>
>
>
>
> The ecm file looks like this:
> --------------------------------------
> cdl_option CYGBLD_GLOBAL_CFLAGS {
> requires { is_substr(CYGBLD_GLOBAL_CFLAGS, " -O2") }
> };
>
>
> Do .ecm files have the same commands as .cdl?
Ah, my error. I thought you wanted this in one of your .cdl files.
You probably need to add some cdl somewhere, something like
cdl_option CYGBLD_GLOBAL_CFLAGS_O2 {
display "Compile with -02"
default 0
no_define
requires { is_substr(CYGBLD_GLOBAL_CFLAGS, " -O2") }
}
And then in your .ecm file
cdl_option CYGBLD_GLOBAL_CFLAGS_O2 {
user_value 1
}
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
next prev parent reply other threads:[~2007-09-12 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 22:54 Mike Arthur
2007-09-12 7:01 ` Andrew Lunn
2007-09-12 17:12 ` Mike Arthur
2007-09-12 18:02 ` Andrew Lunn [this message]
2007-09-12 15:01 ` Sergei Gavrikov
2007-09-12 15:17 ` [ECOS] " Grant Edwards
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=20070912180157.GR3557@lunn.ch \
--to=andrew@lunn.ch \
--cc=arth2219@gmail.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).