This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: CDL template example?
- From: Jonathan Larmour <jlarmour at redhat dot com>
- To: Gary Thomas <gthomas at redhat dot com>
- Cc: Grant Edwards <grante at visi dot com>,eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Wed, 12 Dec 2001 01:23:01 +0000
- Subject: Re: [ECOS] CDL template example?
- References: <20011211163451.A28300@visi.com> <1008113718.15865.66.camel@hermes>
Gary Thomas wrote:
>
> On Tue, 2001-12-11 at 15:34, Grant Edwards wrote:
> >
> > What I'd like is a way to pre-define a configuration that would
> > be the same as the result of doing something like:
> >
> > ecosconfig new foobar
> > ecosconfig remove this-package
> > ecosconfig add that-package theother-package
> > [edit ecos.ecc to set user-values for a handfull of package options]
>
> Use 'ecosconfig import <file>'. While we generally use this to define
> a complete configuration, the file can actually be any CDL .ecm
> fragment. For example, I use this fragment to force ROM startup mode:
>
> ------- startup.ROM -----------
> cdl_component CYG_HAL_STARTUP {
> user_value ROM
> };
>
Although as was only recently discussed here, imported files can't _remove_
packages. For that, you need to have a new template with that package not
included, or use the "next smallest" template and add the missing packages.
(this is now bug 57324)
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine