From: David Brennan <eCos@brennanhome.com>
To: Andy Voelkel <andy@bushtaxi.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Installation problems - ECOS toolset on Windows platform
Date: Fri, 27 May 2005 16:08:00 -0000 [thread overview]
Message-ID: <4296552C.7000203@brennanhome.com> (raw)
In-Reply-To: <E1DbQAJ-0002EA-00@mail.aemf.org>
Andy Voelkel wrote:
>I am trying to bring up the ECOS toolset on a Windows machine. After
>carefully following the installation instructions on the ECOS website
>(including the installation of the Cygwin tools), I tried to fire up the
>configuration tool by double clicking on its icon in a Windows Explorer. I
>got the message:
>
>"This application has failed to start because cygwin1.dll was not found.
>Re-installing the application may fix this problem".
>
>The file cygwin1.dll is indeed on my maching, in C:\progs\cygwin\bin. Is
>this some sort of path or environment variable problem?
>
>
>
Yes. That is not in your path. And see comment below.
>So, I thought I'd try invoking the configuration tool from a bash shell. I
>negotiated my way to the directory containing the executable, and invoked
>it. This time the graphic interface came up, spewed a bunch of text into its
>output window, and closed itself. As best I can tell, many of the error
>messages contained the string "this package does not have any valid version
>subdirectories".
>
>
>
Did you set ECOS_REPOSITORY? Within whatever your basic installation
directory (/opt/ecos) you should have a shell script ecosenv.sh (or
ecosenv.csh). I recommend you run that after starting your bash shell.
>Can anyone help me figure out what is causing these problems?
>
>
>
I imagine the answers to both of these are in the documentation. I don't
have time to look now. But you should before asking.
>While I'm at it, I might as well as whether there are many folks using
>Windows as their ECOS development machine. ECOS is looking to be an
>attractive RTOS choice, but I don't relish the idea of every developer
>needing a second computer just so they can run the ECOS toolset from Linux.
>
>
>
The toolset works "fine" under windows. But you will find the command
line interface is more useful in the long run. It is completely stable
under windows. I have had some issues with the graphical tool. So I have
given up on that. But I use the command-line version just fine under
windows.
>- Andy Voelkel
>
>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-05-26 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 13:29 Andy Voelkel
2005-05-27 16:08 ` David Brennan [this message]
[not found] <20050531215459.9E7EE65C057@smtp.ecoscentric.com>
2005-06-01 5:14 ` Andy Voelkel
2005-06-01 8:27 ` Hans Hübner
2005-06-02 20:53 ` Andy Voelkel
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=4296552C.7000203@brennanhome.com \
--to=ecos@brennanhome.com \
--cc=andy@bushtaxi.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).