From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17582 invoked by alias); 1 Dec 2012 18:30:07 -0000 Received: (qmail 17564 invoked by uid 22791); 1 Dec 2012 18:30:05 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,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; Sat, 01 Dec 2012 18:29:58 +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 326E8234C03E; Sat, 1 Dec 2012 18:29:56 +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 qB1ITtxK001472; Sat, 1 Dec 2012 18:29:55 GMT Message-ID: <50BA4CA3.90307@dallaway.org.uk> Date: Sat, 01 Dec 2012 18:30: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: In-Reply-To: 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/msg00000.txt.bz2 Mike On 29/11/12 23:23, Michael Jones wrote: > But I noticed that it does not copy source files or ecos.db from the > source dir to the target dir along with the binary stuff. > > Is there a way to get all the code and db copied over via the make > process or do I just have to copy it? > > Should I instead compile on top of the source tree directly? When you build eCos, the eCos library (libtarget.a), linker script (target.ld), external header files and a few miscellaneous files are placed in the eCos "install" tree. These files are all you need to compile application code and link it with eCos to form a self-contained application executable. Your application code should not reference header files located within the eCos source code repository. 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