From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31222 invoked by alias); 1 Feb 2007 07:48:34 -0000 Received: (qmail 31207 invoked by uid 22791); 1 Feb 2007 07:48:32 -0000 X-Spam-Check-By: sourceware.org Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 01 Feb 2007 07:48:26 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1HCWg9-0007Jj-00; Thu, 01 Feb 2007 08:48:21 +0100 Date: Thu, 01 Feb 2007 07:48:00 -0000 To: wang cui Cc: ecos-discuss@ecos.sourceware.org Message-ID: <20070201074821.GJ22661@lunn.ch> Mail-Followup-To: wang cui , ecos-discuss@ecos.sourceware.org References: <20070130214625.GG22661@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) From: Andrew Lunn 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] In-built shell for Redboot X-SW-Source: 2007-02/txt/msg00004.txt.bz2 On Thu, Feb 01, 2007 at 01:56:43AM +0000, wang cui wrote: > I think he want to call function by name directly without a warpper of > "RedBoot_cmd()" macro. > > Actually VxWorks provide this function. It strips all symbles from > application image, then generate a source file contains all symbles, then > add it into project and rebuild it. Then user can call all functions > directly from VxWorks shell. > However, I think Redboot style is good enough. > > But what I am thinking about is: Can we divide the shell functionality from > Redboot and create a new package(suppose to be RedShell)? > Because we always need a shell in application, and there are very many > things have been implemented in Redboot. If so, we can reduce a lot of work > in writing application shell. A lot of people have talked about shells, but nobody has ever written a nice, clean, extendable shell package. What needs to happen is somebody needs to write down a design of such a package and ask for comments. Then implement it and again ask for comments. Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss