public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Dan Conti <danc@iobjects.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: TCP/IP as a program.
Date: Thu, 16 Aug 2001 11:04:00 -0000	[thread overview]
Message-ID: <20010816130605.A3777@visi.com> (raw)
In-Reply-To: <D8DFF0AFE792914996F997E68FEC3A48036746@bunker.iobjects.com>

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

  reply	other threads:[~2001-08-16 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16 10:22 Dan Conti
2001-08-16 11:04 ` Grant Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-16  1:29 [ECOS] " David.Karlberg
2001-08-16  7:47 ` [ECOS] " Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010816130605.A3777@visi.com \
    --to=grante@visi.com \
    --cc=danc@iobjects.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).