This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: question on Redboot and CDL template
Dear Bart Veer,
Thank you for your explanation.
Then I have some more questions.
If I define a target in ecos.db as below,
target ixdp425 {
alias { "IXDP425 board" ixdp425 }
packages { CYGPKG_HAL_ARM
CYGPKG_HAL_ARM_XSCALE_CORE
CYGPKG_HAL_ARM_XSCALE_IXP425
CYGPKG_HAL_ARM_XSCALE_IXDP425
CYGPKG_IO_PCI
..............
}
}
However, for initial porting, I need not compile the PCI package into the .bin image. So, how to temporarily remove this
package? Should I remove it from the target definition lines as shown above? Or I need to remove it from the redboot_xxx.ecm
file? Or both?
BTW, where can I find information about the syntax of .ecm file? The online manual seems not provide any so far.
Thank you.
Best Regards,
--
kneep <caozhiyuan@hotmail.com>
On Thu, 22 Apr 2004 09:30:30 +0100 (BST)
Bart Veer <bartv@ecoscentric.com> wrote:
> >>>>> "kneep" == kneep <caozhiyuan@hotmail.com> writes:
>
> kneep> Dear All,
> kneep> Hello!
> kneep> I am compiling the Redboot.
> kneep> If I import a .ecm file before generating the make
> kneep> file, say redboot_rom.ecm, will it replace the
> kneep> configuration that I write in ecos.db? Or ecos.db still
> kneep> works?
>
> Importing a .ecm file will do nothing to the ecos.db packages database
> in the component repository. Instead it will modify your current
> configuration, as described by the ecos.ecc savefile in your build
> tree. It has the same net effect as running up the graphical
> configuration tool and manipulating certain options. For well-defined
> tasks like building RedBoot for a given target, the import is easier
> and more robust.
>
> Bart
>
> --
> Bart Veer eCos Configuration Architect
> http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss