[ECOS] configuration options

[ECOS] configuration options

[Gene Kozin]

Hi,

I'm doing an eCos port and having trouble adding/changing kernel
configuration options in kernel/<version>/include/pkgconf/kernel.h.

Particularly, I want to add CYGNUM_KERNEL_COUNTERS_RTC_PERIOD
#define specific to my platform, similar to those already in
kernel.h, such as:

#if defined(CYG_HAL_MN10300_STDEVAL1)
#define CYGNUM_KERNEL_COUNTERS_RTC_RESOLUTION   {1000000000, 100}
#define CYGNUM_KERNEL_COUNTERS_RTC_PERIOD       150000
#endif

However, no matter what, my mods don't make it into kernel.h in
build/install tree.  What's wrong?

Thanks.

Gene Kozin,
Sr. Firmware Engineer
C-Cube Microsystems

Re: [ECOS] configuration options

[Jesper Skov]

>>>>> "Gene" == Gene Kozin <gkozin@c-cube.com> writes:

Gene> However, no matter what, my mods don't make it into kernel.h in
Gene> build/install tree.  What's wrong?

The pkgconf files are only copied to the build directory the first
time you run pkgconf, or if you use the --force option. This is so to
prevent the configuration files to be accidently overwritten if
enabling/disabling packages.

Jesper

Re: [ECOS] configuration options

[Gene Kozin]

----- Original Message ----- 
From: Jesper Skov <jskov@cygnus.co.uk>
To: Gene Kozin <gkozin@c-cube.com>
Cc: eCos Mailing List <ecos-discuss@sourceware.cygnus.com>
Sent: Tuesday, October 19, 1999 12:48 AM
Subject: Re: [ECOS] configuration options


> >>>>> "Gene" == Gene Kozin <gkozin@c-cube.com> writes:
> 
> Gene> However, no matter what, my mods don't make it into kernel.h in
> Gene> build/install tree.  What's wrong?
> 
> The pkgconf files are only copied to the build directory the first
> time you run pkgconf, or if you use the --force option. This is so to
> prevent the configuration files to be accidently overwritten if
> enabling/disabling packages.
> 
Would it be the case if I do "Save As..." from the Configuration
Tool into a new directory after modifying kernel.h?  It doesn't
seem to work. :-(

-gk

Re: [ECOS] configuration options

[Jesper Skov]

>>>>> "Gene" == Gene Kozin <gkozin@c-cube.com> writes:

>> >>>>> "Gene" == Gene Kozin <gkozin@c-cube.com> writes:
>> 
Gene> However, no matter what, my mods don't make it into kernel.h in
Gene> build/install tree.  What's wrong?
>>  The pkgconf files are only copied to the build directory the first
>> time you run pkgconf, or if you use the --force option. This is so
>> to prevent the configuration files to be accidently overwritten if
>> enabling/disabling packages.
>> 
Gene> Would it be the case if I do "Save As..." from the Configuration
Gene> Tool into a new directory after modifying kernel.h?  It doesn't
Gene> seem to work. :-(

I think so. But you'll also have to make the ConfigTool reload the
file you changed. I don't know if it automatically checks for changed
files in the repository - but according to the behavior you describe
it probably doesn't.

Try forcing it to reload the files by setting the repository path
(just type return/click OK at the requester so the same path is used).

Jesper