This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: About .ecm files
- From: "Dave Airlie" <david dot airlie at parthus dot com>
- To: "Jonathan Larmour" <jlarmour at redhat dot com>
- Cc: "surya prakash" <suryaprakash at multitech dot co dot in>, "Ecos-Discuss " <ecos-discuss at sources dot redhat dot com>
- Date: 10 Dec 2001 12:30:51 +0000
- Subject: Re: [ECOS] About .ecm files
- References: <3C11B4CF.4FB28DFB@multitech.co.in> <3C120EA4.4C48E65E@redhat.com>
>
> .ecm files are "minimal eCos configuration" files. They are almost like a
> savefile, but only register the differences between your configuration and
> the default.
minus any package additions removal... which has bitten me a couple of
times...
not sure if still applies.. but I used to make a .ecc file with packages
from the default system removed, and the .ecm would reflect it but
importing said .ecm file would never change the packages ... I had to
ship the customer the .ecc also..
twas a while ago and I've no idea if I can reproduce it at the moment
:-)
Regards,
Dave.
In this context, they are supplied to give you a "potted"
> configuration to build redboot for various startups.
>
> They're not a required part of the port as such - you can just set the
> options yourself in the configuration - but they are included so that other
> people can build redboot without having to know the details of exactly what
> options to set or packages to add.
>
> 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
--
David Airlie, Software Engineer, Parthus Technologies plc.,
Mary Rosse Centre, National Tech Park, Limerick, Ireland.
t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com