Re: [ECOS] Changed ecc file format in ecosconfig - how to get the old??

[Andrew Lunn <andrew dot lunn at ascom dot ch>]

On Thu, Aug 08, 2002 at 12:11:27PM +0200, Jepsen Hans Peter wrote:
> I have build a new version of ecosconfig from sources downloaded yesterday.

Me too.

> The old format has a lot of comments in it, which was very helpfull when you
> had to do changes to the ecc file.
> In the new format these comments are removed. See example below.

Now this is strange. Here is what's in my ecos.ecc file

# >
# Startup type
# At the moment only ROM startup is supported. In the context
# of the synthetic target this means a read-only region for
# code and a read-write region for data.
#
cdl_component CYG_HAL_STARTUP {
    # Flavor: data
    # No user value, uncomment the following line to provide one.
    # user_value ROM
    # value_source default
    # Default value: ROM
    # Legal values: "ROM"
 
    # The following properties are affected by this value
    # option CYGSEM_HAL_INSTALL_MMU_TABLES
    #     DefaultValue:  CYG_HAL_STARTUP != "RAM" 
  
So i get the full comments. 

I notice you are using an EAVMCAN. This is not a target thats in the
anoncvs tree. Maybe its something to do with your custom HAL? Seems
unlikely, but you never know. 

Try configuring for some other target, say linux, like i have above.

> Here the example:
> 
> The new format:
> 
> cdl_component CYG_HAL_STARTUP {
>     user_value ROM
> };
 
Humm, actually, that looks like part of an import/export file, an .ecm
file, not ecos.ecc. 

      Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss