diff options
Diffstat (limited to '')
| -rw-r--r-- | doc/started/nt.t | 105 |
1 files changed, 44 insertions, 61 deletions
diff --git a/doc/started/nt.t b/doc/started/nt.t index b07261d274..289c58aa76 100644 --- a/doc/started/nt.t +++ b/doc/started/nt.t @@ -1,5 +1,5 @@ @c -@c COPYRIGHT (c) 1988-2002. +@c COPYRIGHT (c) 1988-2010. @c On-Line Applications Research Corporation (OAR). @c All rights reserved. @c @@ -15,31 +15,24 @@ This chapter was originally written by @uref{mailto:g_montel@@yahoo.com, Geoffroy Montel <g_montel@@yahoo.com>} with input from @uref{mailto:<D.J@@fiddes.surfaid.org>, David Fiddes <D.J@@fiddes.surfaid.org>}. -It was based upon his successful but unnecessarily -painful efforts with Cygwin beta versions. -Cygwin and this chapter have been updated multiple times since -those early days although their pioneering efforts -and input is still greatly appreciated. +It was based upon his successful but unnecessarily painful efforts with +Cygwin beta versions. Cygwin and this chapter have been updated multiple +times since those early days although their pioneering efforts and input +is still greatly appreciated. @section Microsoft Windows Version Requirements -RTEMS users report fewer problems when using Microsoft -Windows NT, 2000, or XP. Although, the open source tools -that are used in RTEMS development do execute on Windows 95, -98, or ME, they tend to be more stable when used with -the modern Windows variants. +RTEMS users report fewer problems when using Microsoft Windows XP or newer. @section Cygwin -For RTEMS development, the recommended approach is to use -Cygwin 1.0 or later. Cygwin is available from -@uref{http://sources.redhat.com/cygwin, http://sources.redhat.com/cygwin} -Recent versions of Cygwin are vastly improved over the beta -versions. Most of the oddities, instabilities, and performance -problems have been resolved. The installation procedure -is much simpler. However, there are a handful of issues -that remain to successfully use Cygwin as an RTEMS development -environment. +For RTEMS development, the recommended approach is to use Cygwin. Cygwin +is available from @uref{http://www.cygwin.com, 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. @itemize @bullet @@ -79,18 +72,17 @@ shell scripts properly. filesystem (e.g. mounted with the @code{-b} option). Otherwise, many confusing errors will result. -@item A user has reported that they needed -to set 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). +@item A user has reported that they needed to set @code{CYGWIN=ntsec} +for chmod to work correctly, but had to set @code{CYGWIN=nontsec} +for compile to work properly (otherwise there were complaints about +permissions on a temporary file). @item If you want to build the tools from source, you have the same options as UNIX users. -@item You may have to uncompress archives during this -process. You must @b{NOT} use @code{WinZip} or -@code{PKZip}. Instead the un-archiving process uses -the GNU @code{zip} and @code{tar} programs as shown below: +@item You may have to uncompress archives during this process. You must +@b{NOT} use @code{WinZip} or @code{PKZip}. Instead the un-archiving +process uses the GNU @code{zip} and @code{tar} programs as shown below: @example tar -xzvf archive.tgz @@ -102,20 +94,18 @@ tar -xzvf archive.tgz @section Text Editor -You absolutely have to use a text editor which can -save files with Unix format. So do @b{NOT} use Notepad -or Wordpad! There are a number of editors -freely available that can be used. +You absolutely have to use a text editor which can save files with Unix +format. So do @b{NOT} use Notepad or Wordpad! There are a number of +editors freely available that can be used. @itemize @bullet @item @b{VIM} (@b{Vi IMproved}) is available from -@uref{http://www.vim.org/,http://www.vim.org/}. -This editor has the very handy ability to easily -read and write files in either DOS or UNIX style. +@uref{http://www.vim.org/,http://www.vim.org/}. This editor has the very +handy ability to easily read and write files in either DOS or UNIX style. @item @b{GNU Emacs} is available for many platforms -including MS-Windows. The official homepage -is @uref{http://www.gnu.org/software/emacs/emacs.html, +including MS-Windows. The official homepage is +@uref{http://www.gnu.org/software/emacs/emacs.html, http://www.gnu.org/software/emacs/emacs.html}. The GNU Emacs on Windows NT and Windows 95/98 FAQ is at @uref{http://www.gnu.org/software/emacs/windows/ntemacs.html, @@ -123,11 +113,10 @@ http://www.gnu.org/software/emacs/windows/ntemacs.html}. @end itemize -If you do accidentally end up with files -having MS-DOS style line termination, then you -may have to convert them to Unix format for some -Cygwin programs to operate on them properly. The -program @code{dos2unix} can be used to put them +If you do accidentally end up with files having MS-DOS style line +termination, then you may have to convert them to Unix format for some +Cygwin programs to operate on them properly. The program @code{dos2unix} +can be used to put them back into Unix format as shown below: @example @@ -137,22 +126,16 @@ Dos2Unix: Cleaning file XYZ ... @section System Requirements -Although the finished cross-compiler is fairly easy on resources, -building it can take a significant amount of processing power and -disk space. - -@itemize @bullet - -@item The faster the CPU, the better. The tools and Cygwin can be -@b{very} CPU hungry. - -@item The more RAM, the better. Reports are that when building GCC -and GDB, peak memory usage can exceed 256 megabytes. - -@item The more disk space, the better. You need more if you are building -the GNU tools and the amount of disk space for binaries is obviously -directly dependent upon the number of CPUs you have cross toolsets -installed for. - -@end itemize - +Although the finished cross-compiler is fairly easy on resources, building +it can take a significant amount of processing power and disk space. +Luckily, desktop computers have progressed very far since this guide +was originally written so it is unlikely you will have any problems. +Just do not use an old cast-off machine with < 1 GB RAM and a 1 Ghz CPU. +Unless, of course, you enjoy waiting for things to complete. + +The more disk space, the better. You need more if you are building the +GNU tools and the amount of disk space for binaries is obviously directly +dependent upon the number of CPUs you have cross toolsets installed for. +In addition to the disk space requirements documented earlier for tool +building, you will also have to have enough space to install the Cygwin +environment. |