From 48a7fa31f918a6fc88719b3c9393a9ba2829f42a Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Tue, 15 Nov 2016 10:37:59 -0600 Subject: Remove texinfo format documentation. Replaced by Sphinx formatted documentation. closes #2812. --- doc/started/nt.t | 145 ------------------------------------------------------- 1 file changed, 145 deletions(-) delete mode 100644 doc/started/nt.t (limited to 'doc/started/nt.t') diff --git a/doc/started/nt.t b/doc/started/nt.t deleted file mode 100644 index cb34fd9d66..0000000000 --- a/doc/started/nt.t +++ /dev/null @@ -1,145 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-2010. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. - -@appendix Using MS-Windows as a Development Host - -This chapter discusses the installation of the GNU tool chain -on a computer running the Microsoft Windows operating system. - -This chapter was originally written by -@uref{mailto:g_montel@@yahoo.com, Geoffroy Montel } -with input from -@uref{mailto:, David Fiddes }. -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 XP or newer. - -@section Cygwin - -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 - -@item There is no @code{cc} program by default. The GNU configure -scripts used by RTEMS require this to be present to work properly. -The solution is to link @code{gcc.exe} to @code{cc.exe} as follows: - -@example -ln -s /bin/gcc.exe /bin/cc.exe -@end example - -@item Make sure @code{/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 @code{/bin/sh.exe}, execute -the command @code{/bin/sh --version}. If it looks similar to -the following, then it is GNU Bash and you are OK: - -@example -GNU bash, version 2.04.5(12)-release (i686-pc-cygwin) -Copyright 1999 Free Software Foundation, Inc. -@end example - -If you get an error or it claims to be any other shell, you need -to copy it to a fake name and copy -@code{/bin/bash.exe} to @code{/bin/sh.exe}: - -@example -cd /bin -mv sh.exe old_sh.exe -cp bash.exe sh.exe -@end example - -The Bourne shell has to be present in @code{/bin} directory to run -shell scripts properly. - -@item Make sure you unarchive and build in a binary mounted -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 @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: - -@example -tar -xzvf archive.tgz -@end example - -@code{tar} is provided with Cygwin. - -@end itemize - -@section MingGW - -You might consider choosing MinGW since it provides better perfomance. There is a wiki entry on a MinGW RTEMS toolset installer available at @uref{http://www.rtems.org/wiki/index.php/MinGW_Tools_for_Windows,http://www.rtems.org/wiki/index.php/MinGW_Tools_for_Windows}. Also, there are prebuilt tools for different architectures available for download at @uref{http://www.rtems.org/ftp/pub/rtems/mingw32,http://www.rtems.org/ftp/pub/rtems/mingw32}. - -@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! Basically, any more or less advanced -text editor is usually able to do that. There is a number of editors freely -available that can be used. - -@itemize @bullet -@item @b{Notepad++} has an interface familiar to Windows users and can be downloaded from @uref{http://notepad-plus-plus.org/,http://notepad-plus-plus.org/}. - -@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. - -@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, -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, -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 -back into Unix format as shown below: - -@example -$ dos2unix XYZ -Dos2Unix: Cleaning file XYZ ... -@end example - -@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. -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. -- cgit v1.2.3