From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84923 invoked by alias); 16 Jun 2016 17:09:58 -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 84229 invoked by uid 89); 16 Jun 2016 17:09:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=ellis, ecc, manually, linker-related 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 17:09:44 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bDanR-0005Ky-U0 for ecos-discuss@ecos.sourceware.org; Thu, 16 Jun 2016 19:09:38 +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 19:09:37 +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 19:09:37 +0200 To: ecos-discuss@ecos.sourceware.org From: Grant Edwards Date: Thu, 16 Jun 2016 17:09:00 -0000 Message-ID: References: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50652@exchange> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BB3@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/msg00001.txt.bz2 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. 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). 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. 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. > I have located the .ecc file for my project and have attempted to > rebuild the library but something seems to be amiss. I see the > extras.o, libextras.a and libtarget.a files in _install/lib change > but the target.ld and vectors.o files remain unchanged. You probably need to start with a new build tree. > On one of my changes I updated linker-related files for my hardware > in the eCos repository, but the linker files never seem to be > regenerated. Only the .c files are used directory from the repository. Most other files get processed and then copied into the build tree. > If I manually delete target.ld and rebuild the library then a new > linker file is created. > > Is there something I'm missing here? I have tried cleaning What do you mean by "cleaning"? > and then building but nothing seems to make a difference to the > linker file. If you're using the GUI config tool, I can't really help. If you're using the command-line one, start with an empty directory. Your script should start with ecosconfig new then, as needed ecosconfig add econsonfig del and finally change/set/clear whatever package options you need to cat >.tmp$$.cdl <