For RTEMS development, the recommended approach is to use Cygwin. Cygwin is available from http://www.cygwin.com . The primary issues reported by users of Cygwin is that it is slower on the same hardware than a native GNU/Linux installation and strange issues over carriage return/line feed inconsistencies between UNIX and Windows environments. However, there are a handful of other issues that may turn up when using Cygwin as an RTEMS development environment.
cc
program by default. The GNU configure
scripts used by RTEMS require this to be present to work properly.
The solution is to link gcc.exe
to cc.exe
as follows:
ln -s /bin/gcc.exe /bin/cc.exe
/bin/sh.exe
is GNU Bash. Some Cygwin
versions provide a light Bourne shell which is insufficient to build
RTEMS. To see which shell is installed as /bin/sh.exe
, execute
the command /bin/sh --version
. If it looks similar to
the following, then it is GNU Bash and you are OK:
GNU bash, version 2.04.5(12)-release (i686-pc-cygwin) Copyright 1999 Free Software Foundation, Inc.
If you get an error or it claims to be any other shell, you need
to copy it to a fake name and copy
/bin/bash.exe
to /bin/sh.exe
:
cd /bin mv sh.exe old_sh.exe cp bash.exe sh.exe
The Bourne shell has to be present in /bin
directory to run
shell scripts properly.
-b
option). Otherwise,
many confusing errors will result.
CYGWIN=ntsec
for chmod to work correctly, but had to set CYGWIN=nontsec
for compile to work properly (otherwise there were complaints about
permissions on a temporary file).
WinZip
or PKZip
. Instead the un-archiving
process uses the GNU zip
and tar
programs as shown below:
tar -xzvf archive.tgz
tar
is provided with Cygwin.
Copyright © 1988-2008 OAR Corporation