public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: L D <pocketcoder@rogers.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ECOS - MIPS
Date: Wed, 22 Jun 2005 18:28:00 -0000	[thread overview]
Message-ID: <20050622182844.7476.qmail@web88210.mail.re2.yahoo.com> (raw)
In-Reply-To: <200506221006.59090.sinany@beko.com.tr>

--- "K. Sinan YILDIRIM" <sinany@beko.com.tr> wrote:

> i dont understand why ecos restricts its users with
> a configtool and 

  Have you actually used it the way it was meant to be
used? You have to learn the _ecos_ way of doing
things, there is no shortcuts (unless you pay someone
[not me] to do the work) !.

> templates. i want a clean makefile and module
> structure. 

  What is so unclean about eCos? eCos is more than a
collection of .cxx files held together by makefiles.
It is a collection of reconfigurable reusable
components and this is where the cdl (component
definition language) comes in. Take a look at his link
http://www.embedded.com/story/OEG20011220S0059
  its few years old but it is also nice and _short_. 
  
> not structuring with 
> a config tool or hardware environment. it is really
> diffucult to add or 
> remove a new file. also many files are coupled each
> other. 

  You add and remove files by adding the filename to
the a cdl file. That is not harder than editing a
makefile. 

> 
> i have a board that implements mips core and
> different to atlas board. there 
> must be a clean version of ecos that includes pure
> mips dependencies. atlas 

  There is no such thing as "pure" mips. Why don't you
 just give us more details about your board. It is
much more productive than making negative inaccurate
comments about eCos. This is how it normally works
around here. You ask a question, give the relevant
details and hope that someone can help. 

> dependencies makes people to change their OS
> choice...
> 
> does anyone think that it is really configurable ? 

  Hello! Its called configurable for a good reason!





-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2005-06-22 18:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <W646741726646371119364845@webmail3>
2005-06-22  7:09 ` K. Sinan YILDIRIM
2005-06-22 10:21   ` Fabian Scheler
2005-06-22 18:28   ` L D [this message]
2005-06-23  6:29     ` K. Sinan YILDIRIM
2005-06-23  7:03       ` Andrew Lunn
     [not found]         ` <200506231102.17394.sinany@beko.com.tr>
2005-06-23  8:07           ` K. Sinan YILDIRIM
2005-06-23  8:34             ` Jerome Souquieres
2005-06-23  9:02             ` Andrew Lunn
2005-06-23 10:27               ` K. Sinan YILDIRIM
2005-06-23 15:28                 ` [ECOS] " Grant Edwards
2005-06-24  6:14                   ` K. Sinan YILDIRIM
2005-06-24  9:07                     ` Nick Garnett
2005-06-24 14:08                     ` Grant Edwards
2005-06-24 14:52                       ` K. Sinan YILDIRIM
2005-06-24 16:39                         ` Grant Edwards
2005-06-23 16:19                 ` [ECOS] " Richard Forrest
2005-06-24  0:04                   ` [ECOS] " Grant Edwards
2005-06-24  7:48                     ` Richard Forrest
2005-06-23 15:17             ` Grant Edwards
2005-06-21 13:40 [ECOS] " K. Sinan YILDIRIM
2005-06-21 13:53 ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050622182844.7476.qmail@web88210.mail.re2.yahoo.com \
    --to=pocketcoder@rogers.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).