From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2696 invoked by alias); 11 Jul 2005 21:05:22 -0000 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 Received: (qmail 2685 invoked by uid 22791); 11 Jul 2005 21:05:19 -0000 Received: from smtpauth01.mail.atl.earthlink.net (HELO smtpauth01.mail.atl.earthlink.net) (209.86.89.61) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 11 Jul 2005 21:05:19 +0000 Received: from 68-114-60-24.dhcp.davl.vt.charter.com ([68.114.60.24] helo=[127.0.0.1]) by smtpauth01.mail.atl.earthlink.net with asmtp (Exim 4.34) id 1Ds5Sn-00019N-O7 for ecos-discuss@sources.redhat.com; Mon, 11 Jul 2005 17:05:17 -0400 Message-ID: <42D2DF03.3040407@mindspring.com> Date: Mon, 11 Jul 2005 21:05:00 -0000 From: Frank Pagliughi User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: ecos-discuss@sources.redhat.com References: <42D2B9A4.9010502@spcontrols.com> <20050711185328.GE29363@lunn.ch> In-Reply-To: <20050711185328.GE29363@lunn.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 4d82f965df0f6dd9e3f977c6d1ea408f0a9da525759e26543d9199452a9c0ad610bbe3e673e9067aa2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c Subject: [ECOS] ConfigTool as general library configurator X-SW-Source: 2005-07/txt/msg00126.txt.bz2 Is "configurator" a word? Anyway... I'm working on a library that needs to support multiple platforms from a single code base using lots of conditional compilation, and I keep switching between Windows and Linux hosts. Now that the make files are getting completely out of control, I got to thinking about how nice it would be to have something like the graphical eCos Configtool to configure and recompile my library. Then I thought maybe the Configtool, itself, would work if I wrote a new "ecos.db" database for my library. I've had some initial success, but there's still a couple hurdles: - The Tools|Repository option takes the name of the source tree, rather than the database itself. The name of the database is hard-coded as "ecos.db" - At least one Template is required even though the library may be simple enough to be defined easily with it's targets. - The build requires link scripts, memory maps, and so on, while an application library archiver wouldn't need any of that. (I'm currently stuck on this one). - It appears tied directly to the GNU tools, though with some tweaking should work with most command-line compilers. I think if its tight integration with eCos were loosened a bit, it would be a great general-purpose, open-source, multi-platform, configurable build tool.Does any one else think so? Or are you all just laughing at me? Frank Pagliughi -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss