Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 52 and Version 53 of TBR/UserManual/MinGW_Tools_for_Windows


Ignore:
Timestamp:
09/26/08 05:06:28 (16 years ago)
Author:
ChrisJohns
Comment:

Updated to 4.9.

Legend:

Unmodified
Added
Removed
Modified

  • TBR/UserManual/MinGW_Tools_for_Windows

    v52 v53  
    11= MinGW Tools for Windows =
    22
     3
     4{| border="0" cellpadding="5" cellspacing="0" align="right"
     5|-
     6! style="background:#efefef;" |
     7|}
    38= MinGW Tools for Windows =
    49
    … …  
    712The RTEMS MinGW Tools are packaged in Windows installers. The latest tools can be accessed using the top level installer. It will install the common files and present you with a selection box for the targets you wish to install. The installer will check to see if you already have the target installer present and if present it will not download it again and will install the one you already have.
    813
    9 <blockquote>
    10 <blockquote>
    11 <blockquote>
    12 [http://www.rtems.org/ftp/pub/rtems/windows/4.8/build-17/rtems4.8-tools-17.exe RTEMS Tool Installer (rtems4.8-tools-17.exe)]
    13 </blockquote>
    14 </blockquote>
     14----
     15----
     16<center>'''''Current Release'''''&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[http://www.rtems.org/ftp/pub/rtems/windows/4.9/build-4/rtems4.9-tools-4.exe RTEMS Tool Installer (rtems4.9-tools-4.exe)][[BR]]
     17
     18Previous versions of the tool installers are located at http://www.rtems.org/ftp/pub/rtems/windows/.</center>
     19----
     20----
    1521It is '''recommended you install MinGW, MSYS and MSYS DTK''' before you install the RTEMS Tools. The autotools installer builds autoconf and automake before installing them on your computer. There is no safe way to build autoconf using a cross-build on a Linux host. To build the autotools packages on Windows MSYS and MSYS DTK are required. The autotools installer checks for them and aborts installation if they do not exist. Read the section [wiki:MinGW_Tools_for_Windows#Setting_Up_MinGW  Setting Up MinGW] for details.
    16 </blockquote>
    17 
    18 Previous versions of the tool installers are located at http://www.rtems.org/ftp/pub/rtems/windows/.
    19 
    20 For a detailed walk through of the installer take a look at [wiki:TBR/Delete/Installing_MinGW_RTEMS_Tools Installing MinGW RTEMS Tools].
    21 
    22 The source code for the tools is under the GNU GPL and can be found here http://www.rtems.org/ftp/pub/rtems/windows/4.8/build-17/source. The installers and tools are built and packaged on a Linux Fedora (FC7) computer and the scripts are all provided in the RTEMS source code. Instructions on using the scripts can be found in [wiki:Building/MingwTools Building MinGW Tools].
    23 
    24 The RTEMS Tools are all installed into the default path of <tt>c:\opt\rtems-4.8</tt>. The version number changes with each release. To test the tools run the <tt>rtems.bat</tt> file. This will open a Windows Command prompt (cmd) with a valid path to the installed tools. You can find the <tt>rtems.bat</tt> under the install point or in the '''RTEMS 4.8''' menu under the '''Start Menu'''. Enter the GCC command for your tool set. For example the RTEMS 4.8 ARM GCC command is:
    25 
    26  RTEMS C:\opt\rtems-4.8> arm-rtems4.8-gcc
    27  arm-rtems4.8-gcc: no input files
    28 
    29 A few batch files and a script file are installed into the install point. The first is called <tt>rtems-env.bat</tt>. It sets up the path and environment variables you need to run the RTEMS tools. The second is <tt>rtems.bat</tt>. It will open a Windows command box with the RTEMS tools path and environment set. The last is <tt>sh-run.bat</tt>. You can call this batch file from your editor when you want to compile within the editor. You need to install the MinGW and MSYS packages to use this batch file. For example:
    30 
    31  c:\rtems\arm\sh-run.bat ./vs-make.sh /c/opt/src/rtems/app all
    32 
    33 can be used with Visual Studio and an external make project to compile an application in <tt>c:\opt\src\rtems\app</tt>. The script <tt>vs-make.sh</tt> will change directory and invoke GNU make converting the GCC error messages to the MS format that Visual Studio understands.
    34 = RTEMS 4.9 Tools =
    35 
    36 
    37 Tools for the RTEMS 4.9 release are available at http://www.rtems.org/ftp/pub/rtems/windows/4.9/build-3/.
    38 
    39 Please try these tools and report any issues to the Users mailing list quoting the build number.
    40 
     22----
    4123Before you use these tools install MinGW and MSYS as described above plus also install an newer GNU M4 tools (http://downloads.sourceforge.net/mingw/m4-1.4.7-MSYS.tar.bz2). In the MSYS shell enter:
    4224
    … …  
    6042
    6143Pressing any key will continue how-ever the autoconf and/or automake will not be correct. You should exit the installer and install the required M4 program.
     44
     45For a detailed walk through of the installer take a look at [wiki:TBR/Delete/Installing_MinGW_RTEMS_Tools Installing MinGW RTEMS Tools].
     46
     47The source code for the tools is under the GNU GPL and can be found here http://www.rtems.org/ftp/pub/rtems/windows/4.9/build-4/source. The installers and tools are built and packaged on a Linux Fedora (FC9) computer and the scripts are all provided in the RTEMS source code. Instructions on using the scripts can be found in [wiki:Building/MingwTools Building MinGW Tools].
     48
     49The RTEMS Tools are all installed into the default path of <tt>c:\opt\rtems-4.9</tt>. The version number changes with each release. To test the tools run the <tt>rtems.bat</tt> file. This will open a Windows Command prompt (cmd) with a valid path to the installed tools. You can find the <tt>rtems.bat</tt> under the install point or in the '''RTEMS 4.9''' menu under the '''Start Menu'''. Enter the GCC command for your tool set. For example the RTEMS 4.9 ARM GCC command is:
     50
     51 RTEMS C:\opt\rtems-4.9> arm-rtems4.9-gcc
     52 arm-rtems4.9-gcc: no input files
     53
     54A few batch files and a script file are installed into the install point. The first is called <tt>rtems-env.bat</tt>. It sets up the path and environment variables you need to run the RTEMS tools. The second is <tt>rtems.bat</tt>. It will open a Windows command box with the RTEMS tools path and environment set. The last is <tt>sh-run.bat</tt>. You can call this batch file from your editor when you want to compile within the editor. You need to install the MinGW and MSYS packages to use this batch file. For example:
     55
     56 c:\rtems\arm\sh-run.bat ./vs-make.sh /c/opt/src/rtems/app all
     57
     58can be used with Visual Studio and an external make project to compile an application in <tt>c:\opt\src\rtems\app</tt>. The script <tt>vs-make.sh</tt> will change directory and invoke GNU make converting the GCC error messages to the MS format that Visual Studio understands.
     59= RTEMS 4.10 Tools =
     60
     61
     62Tools for the RTEMS 4.10 release are available at http://www.rtems.org/ftp/pub/rtems/windows/4.10/build-1/.
     63
     64Please try these tools and report any issues to the Users mailing list quoting the build number.
    6265= Setting Up MinGW =
    6366
    … …  
    97100If you do the following stage from an MSYS terminal you will need to update the path to refer to the correct versions of the tools
    98101
    99  > export PATH=/c/opt/rtems-4.8/bin:${PATH}
     102 > export PATH=/c/opt/rtems-4.9/bin:${PATH}
    100103
    101 To build RTEMS with the source code in a directory 'c:\rtems\src\rtems-4.7.99.2' you would do the following:
     104To build RTEMS with the source code in a directory 'c:\rtems\src\rtems-4.9.0' you would do the following:
    102105
    103106 > c:
    104107 > cd \opt\src\rtems
    105  > tar jxf c:\downloads\rtems\rtems-4.7.99.2.tar.bz2
    106  > cd rtems-4.7.99.2
     108 > tar jxf c:\downloads\rtems\rtems-4.9.0.tar.bz2
     109 > cd rtems-4.9.0
    107110 > sh ./bootstrap
    108111 > cd ..
    109112 > mkdir m68k
    110113 > cd m68k
    111  > sh ../rtems-4.7.99.2/configure --target=m68k-rtems4.8 --enable-multilib --prefix=/c/opt/src/rtems/m68k
     114 > sh ../rtems-4.9.0/configure --target=m68k-rtems4.9 --enable-multilib --prefix=/c/opt/src/rtems/m68k
    112115 > sh make all install
    113116
    … …  
    118121If you have checked RTEMS out from CVS you will first need to bootstrap. If you have used Windows to check out from CVS with tools such as [http://www.tortoisecvs.org/ TortoiseCVS] the files will have DOS line endings. This causes problems with autoconf and automake and some files need to be stripped. The RTEMS bootstrap script may be modified to handle this but until then you will need to bootstrap with the following:
    119122
    120  > cd rtems-4.8
     123 > cd rtems-4.9
    121124 > sh find . \( -name \*.ac -o -name \*.m4 -o -name \*.am -o -name \*.in \) -exec dos2unix '{}' \;
    122125 > sh ./bootstrap
    … …  
    126129You can use [http://www.gnu.org/software/emacs/windows/faq2.html Emacs on Windows] to compile RTEMS or your application and use it to track the error messages. To compile enter 'M-x compile' then type
    127130
    128  c:/opt/rtems-4.8/sh-run.bat make -C c:/opt/rtems-4.8/src/rtems-4.8
     131 c:/opt/rtems-4.9/sh-run.bat make -C c:/opt/rtems-4.9/src/rtems-4.9
    129132= Trouble Shooting =
    130133