public inbox for
 help / color / mirror / Atom feed
From: "Michael W. Ellis" <>
To: <>
Subject: [ECOS] eCos Configuration Tool clewan and rebuild
Date: Thu, 16 Jun 2016 13:26:00 -0000	[thread overview]
Message-ID: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BB3@exchange> (raw)
In-Reply-To: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50652@exchange>

I have inherited a project based on eCos 2.0.98 and have reached a point
where I need to rebuild my library.  Most of the folks who originally
worked on this project are no longer with the company and our internal
documentation is scarce at best.

My understanding is that the eCos Configuration Tool is used to make
changes to a .ecc file, and then to use this file to build the library.
I have located the .ecc file for my project and have attempted to
rebuild the library but something seems to be amiss.  I see the
extras.o, libextras.a and libtarget.a files in _install/lib change but
the target.ld and vectors.o files remain unchanged.  On one of my
changes I updated linker-related files for my hardware in the eCos
repository, but the linker files never seem to be regenerated.  If I
manually delete target.ld and rebuild the library then a new linker file
is created.

Is there something I'm missing here?  I have tried cleaning and then
building but nothing seems to make a difference to the linker file.


Before posting, please read the FAQ:
and search the list archive:

  parent reply	other threads:[~2016-06-16 13:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 13:29 [ECOS] cyg_flag_timed_wait doesn't seem to work as expected Michael W. Ellis
2016-05-27 15:53 ` AW: " Richard Rauch
2016-05-27 16:31 ` Nick Garnett
2016-05-27 20:46   ` Michael W. Ellis
2016-06-16 13:26 ` Michael W. Ellis [this message]
2016-06-16 17:09   ` [ECOS] Re: eCos Configuration Tool clewan and rebuild Grant Edwards
2016-06-16 21:18     ` Michael W. Ellis
2016-06-16 21:41       ` Grant Edwards
2016-06-16 23:05         ` Alex Schuilenburg
2016-06-17  4:05           ` AW: " Richard Rauch
2016-06-17 10:10             ` Alex Schuilenburg
2016-06-18 12:01               ` AW: " Richard Rauch
2016-06-18 13:20                 ` Alex Schuilenburg
2016-06-30 14:53         ` [ECOS] Input from debug console Michael W. Ellis
2016-06-30 16:01           ` Michael W. Ellis
2016-06-30 16:09             ` Evgeniy Dushistov
2016-06-30 17:52             ` [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:

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

  git send-email \
    --in-reply-to=07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BB3@exchange \ \ \

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