public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Christian Plessl <cplessl@ee.ethz.ch>
To: "Natarajan, Mekala (CTS)" <NMekala@CHN.CTS-CORP.COM>,
	"'ecos-discuss@sources.redhat.com'"
	<ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] ecos package admin tool
Date: Tue, 12 Dec 2000 04:19:00 -0000	[thread overview]
Message-ID: <5.0.0.25.0.20001212124909.00a88eb0@imap.ee.ethz.ch> (raw)
In-Reply-To: <8F1D166D08ACD41196EE00B0D020944B0BB6A8@CTSINENTSXUB>

Hi mekala

   i used the prebuild binary of the updated configuration tool for
>windows(graphical version 1.3.1.2)..
>since there is no prebuilt package administration tool, i started building
>the tool from the source..
>But i face so many problems in that..is there any prebuilt admistration tool
>in cvs..
>i want to add a ethernet driver package..
>i spent most of the time in installation of package and tools..
>i am not able to concentrate on actual development work..

I would suggest changing your development environment to linux, if this is 
possible for you. My impression is, that most the ecos toolchain and 
installation problems result from using Windows as host platform.

So switching to linux means editing ecos configurations by hand, but so you 
better know what you are doing, hopefully. Further the unix environment 
gives you a lot of very powerfull and conveniant tools for the development 
process. Of course, cygwin tries to give you some of the common tools which 
are included by default (sic!) in any unix environment.

Final remark, this is just my personal impression. I dont think that using 
Linux will solve all problems of the world, but using Linux for ecos 
development will make things easier.

Chris

--
Christian Plessl <cplessl@ee.ethz.ch>

           reply	other threads:[~2000-12-12  4:19 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <8F1D166D08ACD41196EE00B0D020944B0BB6A8@CTSINENTSXUB>]

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=5.0.0.25.0.20001212124909.00a88eb0@imap.ee.ethz.ch \
    --to=cplessl@ee.ethz.ch \
    --cc=NMekala@CHN.CTS-CORP.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).