From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1192 invoked by alias); 31 May 2007 16:41:52 -0000 Received: (qmail 1177 invoked by uid 22791); 31 May 2007 16:41:51 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 31 May 2007 16:41:48 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HtniG-0002Un-Ie for ecos-discuss@sources.redhat.com; Thu, 31 May 2007 18:41:25 +0200 Received: from 87.236.81.130 ([87.236.81.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 May 2007 18:41:24 +0200 Received: from osv by 87.236.81.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 May 2007 18:41:24 +0200 To: ecos-discuss@sources.redhat.com From: Sergei Organov Date: Thu, 31 May 2007 17:09:00 -0000 Message-ID: References: <20070530211229.GI32489@lunn.ch> <20070531151854.GM32489@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.20 (linux) 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: [ECOS] Re: eCos configuration question X-SW-Source: 2007-05/txt/msg00214.txt.bz2 Grant Edwards writes: > On 2007-05-31, Andrew Lunn wrote: >> On Thu, May 31, 2007 at 09:50:50AM -0500, John Mills wrote: >>> Leaving aside my responses to Andrew cut in below: >>> >>> 1. How should I set or clear this switch in my *.ecc files? I >>> don't recognize the entry in 'configtool'. Should I edit >>> the *.ecc and regenerate the tree? Edit the affected >>> 'hal.h'? >> >> You should never need to edit a .h file. I personally never >> use the gui tool. > > I don't think any of the "pros" do. AFAICT, it's just > eye-candy to lessen the initial culture shock for Visual-C > programmers. ;) > >> I find it much easier just to edit the ecos.ecc file and use >> ecosconfig > > That's what I used to do, but I had a hard time keeping track > of what I had changed from the defaults. Now I find it easiest > to write a shell script that creates a source tree. It seems > like a bit of a hassle at first, but you're always sure what > you've got (all your tweaks are in one small file) and you're > always sure you can repeably generate the same source tree. > > ________________________________________________________________________ > #!/bin/bash > set -x > > ecosconfig new foobar net > ecosconfig remove CYGPKG_POSIX > ecosconfig add CYGPKG_IO_I2C > ecosconfig add CYGPKG_FOOBAR_DM2_I2CEEPROM > > cat >.tmp$$.cdl < cdl_option CYGSEM_HAL_DIAG_MANGLER {user_value None} > cdl_option CYGPKG_IO_NFILE {user_value 256} > cdl_option CYGNUM_FILEIO_NFILE {user_value 256} > cdl_option CYGNUM_FILEIO_NFD {user_value 256} > cdl_option CYGPKG_NET_MAXSOCKETS {user_value 256} > cdl_component CYGSEM_KERNEL_SCHED_TIMESLICE {user_value 0} > cdl_option CYGNUM_MEMALLOC_FALLBACK_MALLOC_POOL_SIZE {user_value 0x20} > cdl_option CYGPKG_NET_MEM_USAGE {user_value 0x260000} > cdl_option CYGPKG_NET_NUM_WAKEUP_EVENTS {user_value 40} > cdl_option CYGPKG_NET_BUILD_HW_TESTS {user_value 1} > cdl_option CYGPKG_NET_FREEBSD_INET6 {user_value 0} > EOF > > echo > echo "Importing CDL settings:" > cat .tmp$$cdl > echo > > ecosconfig import .tmp$$.cdl > > ecosconfig tree Yeah, I do almost the same, except I don't generate file to be imported on the fly. "ecosconfig import custom.cdl" is indeed great tool! BTW, if one has edited 'ecos.ecc', he can get initial version of 'custom.cdl' by issuing: $ ecosconfig check $ ecosconfig tree $ ecosconfig export custom.cdl -- Sergei. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss