From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18636 invoked by alias); 4 Dec 2012 16:42:51 -0000 Received: (qmail 18567 invoked by uid 22791); 4 Dec 2012 16:42:49 -0000 X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from tirion.supremecenter202.com (HELO tirion.supremecenter202.com) (209.25.195.243) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 04 Dec 2012 16:42:45 +0000 Received: from [94.234.170.178] (port=38649 helo=[192.168.0.244]) by tirion.supremecenter202.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TfvZy-00045s-CV; Tue, 04 Dec 2012 16:42:42 +0000 Message-ID: <50BE27FF.4020501@siva.com.mk> Date: Tue, 04 Dec 2012 16:42:00 -0000 From: Ilija Kocho User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: John Dallaway CC: Michael Jones , eCos Discussion References: <50BA4CA3.90307@dallaway.org.uk> <27451076-2A19-4F5B-8D40-DAD018AB696D@linear.com> <50BB197D.90400@dallaway.org.uk> In-Reply-To: <50BB197D.90400@dallaway.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: Re: [ECOS] Re: Installing source after full build X-SW-Source: 2012-12/txt/msg00018.txt.bz2 John If there is a wish list, I think it would be a good idea to have an option [in configtool/ecosconfig] to copy the sources into the /build/ tree. Production of private [to the project] eCos instant would be of help for some applications [that need certification, etc]. Ilija On 02.12.2012 10:03, John Dallaway wrote: > 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