diff --git a/documentation/README.1st b/documentation/README.1st index 70a2d6b22..08b53a9ae 100644 --- a/documentation/README.1st +++ b/documentation/README.1st @@ -131,7 +131,7 @@ Software requirements versions of vendor C and C++ compilers may be used for native compilation. Perl - You must have perl version 5.8 or later installed. The configure files do + You must have perl version 5.8.1 or later installed. The configure files do not specify the perl full pathname. You need the perl executable in your search path. @@ -153,7 +153,7 @@ Software requirements support packages. Consult the vxWorks documentation for details. RTEMS - For RTEMS targets, you must use RTEMS version 4.9.2 or later. + For RTEMS targets, you need RTEMS core and toolset version 4.9.2 or later. GNU readline or Tecla library GNU readline and Tecla librararies can be used by the IOC shell to provide @@ -177,8 +177,11 @@ Host system storage requirements Documentation EPICS documentation is available on the WWW via the EPICS home page at APS: - URL http://www.aps.anl.gov/epics available on the IOC software, Base R3.14, - release number, web page which can be accessed from the APS EPICS home page. + URL http://www.aps.anl.gov/epics by selecting IOC software/ Base R3.14/ + . + + Release specific documentation can be found in the base/documentation + directory of the distribution. WWW pages @@ -485,7 +488,7 @@ Example application and extension to quickly implement a complete EPICS system and be able to run channel access clients on the host system. - Also, a perl script, makeBaseExt.pl, is included in the distribution file. + A perl script, makeBaseExt.pl, is included in the distribution file. This script will create a sample extension that can be built and executed. The makeBaseApp.pl and makeBaseExt.pl scripts are installed into the install location bin/ directory during the base build. diff --git a/documentation/README.html b/documentation/README.html index db9633b02..c99396603 100644 --- a/documentation/README.html +++ b/documentation/README.html @@ -25,6 +25,7 @@ README.html
  • Multiple host platforms
    • +

    What is EPICS base?

    The Experimental Physics and Industrial Control Systems (EPICS) is an extensible set of software components and tools with @@ -35,12 +36,15 @@ README.html function. EPICS base allows an arbitrary number of target systems, IOCs (input/output controllers), and host systems, OPIs (operator interfaces) of various types.
    +

    What is new in this release?

    Please check the RELEASE_NOTES file in the distribution for description of changes and release migration details.
    +

    Copyright

    Please review the COPYRIGHT* files included in the distribution for legal terms of usage.
    +

    Supported platforms

    Currently this version of EPICS base has been built on the following hosts for the following targets. If you are trying to build @@ -50,6 +54,7 @@ README.html the base/configure/os/directory. You can start by copying existing configuration files in the configure/os directory and then make changes for your new platforms.
    +

    Host platforms (operating system - architecture [- alternate toolset])

    @@ -74,6 +79,7 @@ win32-x86-mingw (WIN32 API, uses MS dlls) win32-x86-cygwin (WIN32 API, uses MS dlls)
    +

    Cross compile target platforms (operating system - architecture)

    linux-386
@@ -113,6 +119,7 @@ RTEMS-uC5282
    +

    Supported compilers

    This version of EPICS base has been built and tested using the host vendor's C and C++ compilers as well as the GNU gcc and g++ @@ -120,25 +127,32 @@ RTEMS-uC5282 cross-compiled targets. You may need the host vendor's C++ compiler in your search path to do EPICS builds. Check definitions of CC and CCC in base/configure/os/CONFIG.<host>.<host>.
    +

    Software requirements

    +
    GNU make
    You must use GNU make, gnumake, for any EPICS builds. Set your path so that a gnumake version 3.81 or later is available. +

    gcc
    For most cases, you must have gcc version 3.4.2 or later. Appropriate versions of vendor C and C++ compilers may be used for native compilation.

    +

    Perl -
    You must have perl version 5.8 or later installed. The configure +
    You must have perl version 5.8.1 or later installed. The configure files do not specify the perl full pathname. You need the perl executable in your search path.

    +

    Unzip and tar (Winzip on WIN32 systems)
    You must have tools available to unzip and untar the EPICS base distribution file.

    +

    Target systems
    EPICS supports IOCs running on embedded platforms such as VxWorks and RTEMS via cross-compilers. EPICS also supports ?soft? IOCs running as processes on the host platform.

    +

    Tornado 2
    You must have Tornado 2 installed if any of your target systems are vxWorks systems. Tornado 2 provides the cross-compiler and header files @@ -146,8 +160,9 @@ RTEMS-uC5282 Tornado 2 should be specified in the base/configure/RELEASE or base/configure/RELEASE.<hostarch> file. You will also need one or more board support packages. Consult the vxWorks documentation for details.

    +

    RTEMS -
    For RTEMS targets, you must use RTEMS version 4.9.2 or later.

    +
    For RTEMS targets, you need RTEMS core and toolset version 4.9.2 or later.

    GNU readline or Tecla library
    GNU readline and Tecla librararies can be used by the IOC shell to provide command line editing and command line history recall and edit. @@ -169,9 +184,12 @@ RTEMS-uC5282

    Documentation

    EPICS documentation is available on the WWW via the EPICS home page at APS: URL - http://www.aps.anl.gov/epics available on the IOC software, Base - R3.14, release number, web page which can be accessed from the APS - EPICS home page.
    + http://www.aps.anl.gov/epics by selection IOC software/ Base + R3.14/ . +
    +
    Release specific documenataion can be found in the base/documentation +directory of the distribution. +

    WWW pages

    EPICS home page at APS

    @@ -546,7 +564,7 @@ Build choices. Specify target archs.
    access clients on the host system.
    - Also, a perl script, + A perl script, makeBaseExt.pl, is included in the distribution file. This script will create a sample extension that can be built and executed. The makeBaseApp.pl and makeBaseExt.pl scripts are installed into the