From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: NIOS2 toolchain build failure under Cygwin
Date: Wed, 09 Aug 2006 14:31:00 -0000 [thread overview]
Message-ID: <20060809143136.C9F6654395@rivatek.dnsalias.net> (raw)
In-Reply-To: <20060809140718.GE19600@lunn.ch>
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?
That would solve the problem very nicely: one "stock"
repository and one "custom" one containing HALs and whatever
other packages are too ugly (or just not generally useful
enough) to make it into the standard source tree.
> The configtool however does not understand the list thing.
> However, since you are talking about build scripts, i doubt
> that matters for you.
Hmm.
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. ;)
Right now when we decide to sync our eCos repository with the
"official" one, there always seems to be glitches.
--
Grant Edwards grante Yow! .. bleakness....
at desolation.... plastic
visi.com forks...
--
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:31 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 [this message]
2006-08-09 14:55 ` Andrew Lunn
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=20060809143136.C9F6654395@rivatek.dnsalias.net \
--to=grante@visi.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).