From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15880 invoked by alias); 2 Dec 2012 09:04:05 -0000 Received: (qmail 15866 invoked by uid 22791); 2 Dec 2012 09:04:04 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_SPAMHAUS_DROP,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from tetra.codeconfidence.com (HELO tetra.codeconfidence.com) (94.229.66.225) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 02 Dec 2012 09:03:59 +0000 Received: from cog.dallaway.org.uk (cpc1-cmbg10-0-0-cust34.5-4.cable.virginmedia.com [81.102.132.35]) by tetra.codeconfidence.com (Postfix) with ESMTP id 17ADF171AE73; Sun, 2 Dec 2012 09:03:58 +0000 (GMT) Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id qB293vAV024775; Sun, 2 Dec 2012 09:03:57 GMT Message-ID: <50BB197D.90400@dallaway.org.uk> Date: Sun, 02 Dec 2012 09:04:00 -0000 From: John Dallaway User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120606 Thunderbird/10.0.5 MIME-Version: 1.0 To: Michael Jones CC: eCos Discussion References: <50BA4CA3.90307@dallaway.org.uk> <27451076-2A19-4F5B-8D40-DAD018AB696D@linear.com> In-Reply-To: <27451076-2A19-4F5B-8D40-DAD018AB696D@linear.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 Subject: [ECOS] Re: Installing source after full build X-SW-Source: 2012-12/txt/msg00004.txt.bz2 Mike On 01/12/12 20:24, Michael Jones wrote: > I could be wrong, but my observation was the ecos.db was not copied from > the build (meaning the ecos and ecos config tool build), and neither was > packages. The eCos Configuration tool certainly needs ecos.db, but I > assume it needs the package tree. So unless there is some environment > variable telling the Configuration tool where to find this, how would > copying only the library work? > > Perhaps you interpreted my build as the build done within the config tool. Yes, that is where the eCos run-time code is built. > I am talking about the build of ecos and the config tool. Only the host tools are built via the configure/make process. You should point the eCos Confiiguration Tool at your eCos repository (using the Build->Repository menu item) to configure and build the eCos run-time code. You should specify the directory _containing_ the eCos "packages" directory (not the "packages" directory itself). > I am compiling > the whole thing rather than using a binary distribution so that I have > access to the new Kinetis support. You should be able to use the latest Linux-hosted configtool snapshot build (2011-02-09) on 64-bit distros if you install the relevant 32-bit compatibility libraries. Ref: http://ecos.sourceware.org/ml/ecos-discuss/2011-02/msg00031.html I hope this helps... John Dallaway eCos maintainer http://www.dallaway.org.uk/john -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss