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: Re: TCP/IP as a program.


On Thu, Aug 16, 2001 at 10:22:27AM -0700, Dan Conti wrote:
> > -----Original Message-----
> > From: Grant Edwards [mailto:grante@visi.com]
> > Subject: [ECOS] Re: TCP/IP as a program.
> >
> > When testing, you do have to remember to do two makes: one to 
> > recompile the 
> > changed eCos source files, and a second to re-link your test app with
> > the new eCos libraries.  I've created more confusion that I'd like to
> > admit by by forgetting that second make. 
> 
> One thing that just occurred to me, are any of the files in install/lib
> updated every time eCos is built? if so, it seems like you could make
> your test app be dependant on that. I've been meaning to set up a
> makefile that forces a automatic relink if the eCos libs change, for the
> exact same reason as you state above. :)

Yes, my application's make file has dependancies on the eCos
libraries.  But you still have to remember to do a "make" in
the application program's directory.  What I meant was to
either do the eCos make from the test app's makefile or vice
versa.  That way only one "make" is needed.

-- 
Grant Edwards
grante@visi.com


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