From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36911 invoked by alias); 17 Jun 2016 10:10:20 -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 36894 invoked by uid 89); 17 Jun 2016 10:10:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1870, folders, rauch, Rauch X-HELO: mail-wm0-f43.google.com Received: from mail-wm0-f43.google.com (HELO mail-wm0-f43.google.com) (74.125.82.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 17 Jun 2016 10:10:09 +0000 Received: by mail-wm0-f43.google.com with SMTP id v199so223899127wmv.0 for ; Fri, 17 Jun 2016 03:10:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=TVSusWtQDUbieyt6P+3xBu0d4hjt8wz5gRdaovsNCbM=; b=fSomivDJt5TorxX8+X6YbE4oPOS/3qTTZQAaFqnHtL0cSMqUFM3XDQNK2GQXq7h0wY 9yLBI0LKyemS04SIzkQy4AJ1cOToXvLXMlMonODhIhT9U6wgkUZ4RUjaarSLoRavkU/O etlvi3Vps18LSAJJKr2o1jZCRI52aPShkbmaPWej3CxrvFXZ/UELgH4Qxl5uZUbFaimo NShfR0j6k42Um+dTyLi+wmSz0xldXBvA6mghoOZslTOYlcYFewwlSHJqyQGUQBiKbUqD iU8zEnvzxl6Aa80pbXn1NEfOUzHS+/FQPq5nD/Mf3zqMGEkqVTCFO8T6b2HZx2ZVz54r rRuw== X-Gm-Message-State: ALyK8tJ0wX5VUSrLJpHin8sGtwoc0+B+WZ49lD2N5CwiEpBRA3XLISc/q15ogY6YN5/BEg== X-Received: by 10.28.101.134 with SMTP id z128mr20171407wmb.71.1466158205594; Fri, 17 Jun 2016 03:10:05 -0700 (PDT) Received: from [192.168.7.24] ([87.127.120.188]) by smtp.googlemail.com with ESMTPSA id r16sm2861722wmb.23.2016.06.17.03.10.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Jun 2016 03:10:04 -0700 (PDT) To: ecos-discuss@ecos.sourceware.org References: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50652@exchange> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BB3@exchange> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BF3@exchange> <576330BB.7080803@schuilenburg.org> <030f01d1c84d$6d0cafc0$47260f40$@itrgmbh.de> From: Alex Schuilenburg Message-ID: <5763CC7C.7080606@schuilenburg.org> Date: Fri, 17 Jun 2016 10:10:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <030f01d1c84d$6d0cafc0$47260f40$@itrgmbh.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: AW: [ECOS] Re: eCos Configuration Tool clewan and rebuild X-SW-Source: 2016-06/txt/msg00006.txt.bz2 On 17/06/16 05:05, Richard Rauch wrote: > There is one issue maybe. When we are changing major things in our eCos > configuration, we delete the complete build tree folders with file system. > Then the config tool is forced to rebuild everything. > The folders are somehow named like .\.......build and .\....install\. They > are located relative to your path, where the .ecc file is. These are created _install and _build where is the base name of the saved .ecc file. Yes, when using the anoncvs GUI configtool the safest method when changing configurations is to delete all and rebuild. However, the anoncvs GUI configtool has a subtle major flaw when creating a configuration by selecting a target that is not the default. All new target configurations are created against the current target and template (often default target and "default" template), and switched to the new target (and/or template). If you have two similar but distinct targets you could end up with conflicts that the anoncvs GUI tool cannot resolve automatically. Even creating a new configuration for the default target can and often does result in a slightly different configuration (but entirely valid) to that created by ecosconfig. If you are using the anoncvs tools, the safest way to create a new configuration is to use "ecosconfig" - it is the tool that almost all eCos maintainers outside eCosCentric use. eCosPro users should upgrade to version 3.1.10 of the Host Tools which exhibit none of the anoncvs host tools issues - new configurations created by both tools are identical - and use the "File->New Target" functionality illustrated in http://www.ecoscentric.com/ecospro/doc/html/user-guide/using-configtool-win= dows-linux.html -- Alex http://www.ecoscentric.com/ The eCos Experts -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss