This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Header files to install directory


Here's the info from the makefile in the "hal\arm\edb7xxx\current"
directory pertaining to my header file that I've been modifying.

$(PREFIX)/include/cyg/hal/hal_edb7xxx.h:
$(REPOSITORY)/$(PACKAGE)/include/hal_edb7xxx.h
	@mkdir -p $(dir $@)
	@cp $< $@
	@chmod u+w $@

It looks like it should work.  Maybe the tool doesn't do a "make
headers" like it's supposed to?

I'll try the date thing when I get around to adding stuff to the header
file again.  I'll try a manual "make" and a manual "make headers" as
well to see if that makes a difference if it doesn't work again.

> -----Original Message-----
> From: Bart Veer [mailto:bartv@redhat.com] 
> Sent: Wednesday, June 27, 2001 10:19 AM
> To: tadams@extremeeng.com
> Cc: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] Header files to install directory
> 
> 
> >>>>> "Trenton" == Trenton D Adams <tadams@extremeeng.com> writes:
> 
>     Trenton> hal_edb7xxx.h was never updated when I did a build from
>     Trenton> the GUI tool's menu.
> 
>     Trenton> v1.3.1.2
> 
> So take a look at the generated makefile which is supposed to 
> be doing the work, presumably hal/arm/edb7xxx/current in your 
> build tree. That should contain a suitable dependency between 
> the file in the install tree and the one in the source tree. 
> Does it? Also look at the timestamps of the files in 
> question. Is the one you have edited in the repository really 
> more recent than the one in the install tree? 
> 
> Bart
> 
>     >> -----Original Message-----
>     >> From: Bart Veer [mailto:bartv@redhat.com] 
>     >> Sent: Wednesday, June 27, 2001 5:34 AM
>     >> To: tadams@extremeeng.com
>     >> Cc: ecos-discuss@sources.redhat.com
>     >> Subject: Re: [ECOS] Header files to install directory
>     >> 
>     >> 
>     >> >>>>> "Trenton" == Trenton D Adams 
> <tadams@extremeeng.com> writes:
>     >> 
>     Trenton> Do I have to copy header files that I've modified from
>     Trenton> the eCos Repository over to the install directory where
>     Trenton> my libraries are created every single time I update them?
>     Trenton> I thought the config tool was supposed to create the
>     Trenton> header files for you based on the source in the eCos
>     Trenton> repository!
>     >> 
>     >> If you have modified the configuration by e.g. editing 
>     >> ecos.ecc then new versions of the <pkgconf/xxx.h> headers 
>     >> will need to be generated. This happens when you run 
>     >> 'ecosconfig tree', or the equivalent operation from 
> the GUI tool.
>     >> 
>     >> If you have edited an existing file in the repository, e.g. 
>     >> isoinfra/current/include/stdio.h, then the makefiles 
>     >> generated by ecosconfig or the GUI tool should automatically 
>     >> update the copy in the install tree when you next run make. 
>     >> If you look at the generated makefiles you should see the 
>     >> rules which take care of this.
>     >> 
>     >> If have created a new header file then the generated 
>     >> makefiles will not know abut this file and it is necessary to 
>     >> generate new makefiles by running 'ecosconfig tree' again.
>     >> 
>     >> Bart
>     >> 
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]