From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 77013 invoked by alias); 16 Jun 2016 21:18:21 -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 76997 invoked by uid 89); 16 Jun 2016 21:18:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.1 required=5.0 tests=AWL,BAYES_50,RDNS_DYNAMIC,TVD_RCVD_IP autolearn=no version=3.3.2 spammy=ecos-discuss-owner@ecos.sourceware.org, U*ecos-discuss-owner, ecosdiscussownerecossourcewareorg, H*RU:sk:exchang X-HELO: exchange.hsv.pesa.com Received: from 67-63-150-35.arpa.kmcmail.net (HELO exchange.hsv.pesa.com) (67.63.150.35) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 16 Jun 2016 21:18:10 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 16 Jun 2016 21:18:00 -0000 Message-ID: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BF3@exchange> In-Reply-To: References: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50652@exchange> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BB3@exchange> From: "Michael W. Ellis" To: X-IsSubscribed: yes Subject: RE: [ECOS] Re: eCos Configuration Tool clewan and rebuild X-SW-Source: 2016-06/txt/msg00002.txt.bz2 > -----Original Message----- > From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss- > owner@ecos.sourceware.org] On Behalf Of Grant Edwards > Sent: Thursday, June 16, 2016 12:10 PM > To: ecos-discuss@ecos.sourceware.org > Subject: [ECOS] Re: eCos Configuration Tool clewan and rebuild >=20 > On 2016-06-16, Michael W. Ellis wrote: > > I have inherited a project based on eCos 2.0.98 and have reached a > > point where I need to rebuild my library. Most of the folks who > > originally worked on this project are no longer with the company and > > our internal documentation is scarce at best. > > > > My understanding is that the eCos Configuration Tool is used to make > > changes to a .ecc file, and then to use this file to build the > library. >=20 > Yes. However, there are two different ecos configuration tools. A > command line one, and a GUI one (there might be multiple similar but > different look/feel GUI ones, I don't really know). >=20 > For all our actuall production code, we use the command-line ecosconfig > utility exclusivly. That way you can write a shell script that calls > the ecosconfig utility to generate an .ecc file from scratch and then > creates the build tree. >=20 > That shell script is then placed under source control just like the > rest of source code. IMO, relying on a GUI tool and > accurate/repeatable human clicking for building production code is a > huge mistake. You can place the .ecc file under version control if you > want, but (IMO) it's far more important that the script that _builds_ > the .ecc file is under source control. 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. You asked what I meant by "cleaning". The GUI tool basically has three build options: clean, library and tests. I had tried using the build clean option, expecting it to remove all intermediate and output files (including my linker file) but this didn't seem to do what I expected. Thanks for the tips. This has helped clarify the situation immensely. Michael -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss