From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1034 invoked by alias); 26 May 2005 21:45:34 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 624 invoked by uid 22791); 26 May 2005 21:45:28 -0000 Received: from narya.aemf.org (HELO mail.aemf.org) (66.251.28.161) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 26 May 2005 21:45:28 +0000 Received: from [10.1.1.119] (helo=LatiDroid) by mail.aemf.org with esmtp (Exim 3.36 #1) id 1DbQAJ-0002EA-00 for ecos-discuss@ecos.sourceware.org; Thu, 26 May 2005 14:45:19 -0700 From: "Andy Voelkel" To: Date: Fri, 27 May 2005 13:29:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: X-Scanner: exiscan *1DbQAJ-0002EA-00*pgo//H6sMxw* X-Scanner: exiscan *1DbQAJ-0002EA-00*pgo//H6sMxw* Subject: [ECOS] Installation problems - ECOS toolset on Windows platform X-SW-Source: 2005-05/txt/msg00348.txt.bz2 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? 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". Can anyone help me figure out what is causing these problems? 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. - 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