RE: [ECOS] TCP/IP as a program.

RE: [ECOS] TCP/IP as a program.

[David.Karlberg]

I want to use PPP with TCP/IP and I figured it would be a lot easier to work
with the Net pack 
if I did not have to recompile the whole eCos everytime I want to see if my
changes work.
And that I would have more control of which files are used.

David

-----Original Message-----
From: Andrew Lunn [ mailto:andrew.lunn@ascom.ch ]
Sent: den 16 augusti 2001 10:20
To: Karlberg David
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] TCP/IP as a program.


> Hi,
> I am trying to run the TCP/IP stack as a "program". As opposed to haveing
it
> in the eCos lib. 

Silly question: Why?

        Andrew

Re: [ECOS] TCP/IP as a program.

[Andrew Lunn]

On Thu, Aug 16, 2001 at 10:29:10AM +0200, David.Karlberg@combitechsystems.com wrote:

> I want to use PPP with TCP/IP and I figured it would be a lot easier
> to work with the Net pack if I did not have to recompile the whole
> eCos everytime I want to see if my changes work. And that I would
> have more control of which files are used.

OK. From experiance, i found its fine working on eCos sources
directly. Compiles are no slower working inside ecos to outside. You
may want to look at putting source files into the work tree, rather
than the repository. This is in the documentation somewhere. Just be
carefull of make clean, and ecosconfig tree!

        Andrew

[ECOS] Re: TCP/IP as a program.

[Grant Edwards]

David.Karlberg@combitechsystems.com writes:

> I want to use PPP with TCP/IP and I figured it would be a lot easier to work
> with the Net pack 
> if I did not have to recompile the whole eCos everytime I want to see if my
> changes work.

A make will only recompile files that have changed.  The only time
everything gets recompiled is when you change the eCos configuration
file (ecos.ecc), and if you do that, you've got to re-compile everything 
anyway (regardless of where the files are). 

I regularly work by modifying files in the main eCos source tree, and
I don't think you're going to save much time by splitting out parts of
it. 

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. 

> And that I would have more control of which files are used.

I guess I never had any problems with that. 

-- 
Grant Edwards
grante@visi.com 

RE: [ECOS] Re: TCP/IP as a program.

[Dan Conti]

> -----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. :)

-Dan

Re: [ECOS] Re: TCP/IP as a program.

[Grant Edwards]

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