From: "Dan Conti" <danc@iobjects.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Re: TCP/IP as a program.
Date: Thu, 16 Aug 2001 10:22:00 -0000 [thread overview]
Message-ID: <D8DFF0AFE792914996F997E68FEC3A48036746@bunker.iobjects.com> (raw)
> -----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
next reply other threads:[~2001-08-16 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 10:22 Dan Conti [this message]
2001-08-16 11:04 ` Grant Edwards
-- 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=D8DFF0AFE792914996F997E68FEC3A48036746@bunker.iobjects.com \
--to=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).