From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21162 invoked by alias); 9 Aug 2006 14:55:21 -0000 Received: (qmail 21154 invoked by uid 22791); 9 Aug 2006 14:55:20 -0000 X-Spam-Check-By: sourceware.org Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 Aug 2006 14:55:18 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1GApSj-000676-00; Wed, 09 Aug 2006 16:55:13 +0200 Date: Wed, 09 Aug 2006 14:55:00 -0000 To: Grant Edwards Cc: ecos-discuss@ecos.sourceware.org Message-ID: <20060809145513.GF19600@lunn.ch> Mail-Followup-To: Grant Edwards , ecos-discuss@ecos.sourceware.org References: <20060809134456.822DA54394@rivatek.dnsalias.net> <20060809140718.GE19600@lunn.ch> <20060809143136.C9F6654395@rivatek.dnsalias.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060809143136.C9F6654395@rivatek.dnsalias.net> User-Agent: Mutt/1.5.12-2006-07-14 From: Andrew Lunn X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Re: NIOS2 toolchain build failure under Cygwin X-SW-Source: 2006-08/txt/msg00063.txt.bz2 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