From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 108925 invoked by alias); 16 Jun 2016 21:41:44 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 108907 invoked by uid 89); 16 Jun 2016 21:41:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=one, Sure, BUY, tracked X-HELO: plane.gmane.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Thu, 16 Jun 2016 21:41:33 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bDf2U-0002iX-5G for ecos-discuss@ecos.sourceware.org; Thu, 16 Jun 2016 23:41:26 +0200 Received: from 67-130-15-94.dia.static.qwest.net ([67.130.15.94]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Jun 2016 23:41:26 +0200 Received: from grant.b.edwards by 67-130-15-94.dia.static.qwest.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Jun 2016 23:41:26 +0200 To: ecos-discuss@ecos.sourceware.org From: Grant Edwards Date: Thu, 16 Jun 2016 21:41:00 -0000 Message-ID: References: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50652@exchange> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BB3@exchange> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BF3@exchange> User-Agent: slrn/1.0.2 (Linux) X-IsSubscribed: yes Subject: [ECOS] Re: eCos Configuration Tool clewan and rebuild X-SW-Source: 2016-06/txt/msg00003.txt.bz2 On 2016-06-16, Michael W. Ellis wrote: > Our approach in the past was to use the GUI tool but I agree that > your approach is better since the script file more or less > self-documents the process and is easily tracked under revision > control. Getting from the GUI based configuration to script based > configuration requires some trial and error grunt work with file > comparison tools to figure out exactly what options were changed in > the GUI but it's probably worth it in the long run. Yep, reverse-engineering a script from an existing .ecc file is a bit of a chore, but I think it's probably worth it. Like you said, it takes a bit of of file comparison. If enough work was done up-front so that there's a template that includes the proper set of packages it's possible that you won't need much more more than "ecosconfig new " "ecosconfig tree" ... with perhaps a few option settings in between. You can also add new templates or change existing ones so that you have to do fewer "ecosconfig add" and "ecosconfig del" commands in your script. That's mostly a matter of personal taste. > You asked what I meant by "cleaning". The GUI tool basically has > three build options: clean, library and tests. Ah. I don't know what exactly what the GUI does when you tell it to "clean". It might just do a "make clean", or it might remove everything except the .ecc file and do an "ecosconfig tree". BTW: I've been assuming you're doing development on a *nix host. If you're doing it under Windows+Cywgin, pretty much all the advise applies, but you end up with a whole extra layer of possible issues with Cygwin. -- Grant Edwards grant.b.edwards Yow! An INK-LING? Sure -- at TAKE one!! Did you BUY any gmail.com COMMUNIST UNIFORMS?? -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss