From: Andrew Lunn <andrew@lunn.ch>
To: Grant Edwards <grante@visi.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: NIOS2 toolchain build failure under Cygwin
Date: Wed, 09 Aug 2006 14:55:00 -0000 [thread overview]
Message-ID: <20060809145513.GF19600@lunn.ch> (raw)
In-Reply-To: <20060809143136.C9F6654395@rivatek.dnsalias.net>
On Wed, Aug 09, 2006 at 09:31:36AM -0500, Grant Edwards wrote:
> In gmane.os.ecos.general, you wrote:
> >> It sure would be a lot easier to manage if the HAL was separate
> >> from the main eCos tree. Have a huge tree of "off the shelf"
> >> stuff with one modified file and one buried directory of
> >> "custom" stuff is a real PITA to manage in a production
> >> environment.
> >
> > ecosconfig understands ECOS_REPOSITORY being a list of directories.
> > So you could have a repository of your own which just contains your
> > HAL.
>
> Cool. How did I not know that?
Im not sure its actually documented somewhere. It is something Bart
added a few years back. Im guessing eCosCentric use it internally to
keep customer specific packages seperate from there customer
independent packages.
> It would matter to me personally, but I think in the past there
> have been customers who used the configtool to customize the
> product's firmware. It sure would be easier to maintain if the
> "custom" stuff was in a separate repository. I think it would
> be worth giving up the configtool -- especially since it's
> somebody else that doing the giving up. ;)
At the time it was added, John commented that it required some work to
make configtool support this. So i was never added. To me it seems
like the configtool is unmaintained anyway. If it stays like this, i
would suggest it is dropped in the next official release. This is a
shame given that there has been some recent interest in bringing it up
to date with recent versions of xWidgets and make it build using
automake.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-08-09 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 8:14 Øyvind Harboe
2006-08-09 13:45 ` Grant Edwards
2006-08-09 14:07 ` Andrew Lunn
2006-08-09 14:31 ` Grant Edwards
2006-08-09 14:55 ` Andrew Lunn [this message]
2006-08-21 22:28 ` [ECOS] Configtool with mulitiple repository support Andy Jackson
2006-08-09 15:20 ` [ECOS] Re: NIOS2 toolchain build failure under Cygwin Bart Veer
2006-08-09 15:58 ` Øyvind Harboe
2006-08-09 16:36 ` Grant Edwards
2006-08-09 20:05 ` Bart Veer
2006-08-09 20:28 ` Øyvind Harboe
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 12:25 [ECOS] " Øyvind Harboe
2006-08-08 12:57 ` [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=20060809145513.GF19600@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=grante@visi.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).