From a5aa5c1543b3ec7b2af3a75b1b79d002a5cb4704 Mon Sep 17 00:00:00 2001 From: "Janet B. Anderson" Date: Thu, 13 Sep 2001 16:19:09 +0000 Subject: [PATCH] Updated for R3.14.0.beta1. --- README | 47 ++++---- README.htm | 100 ++++++++++-------- ...DMEconvertingR3.14.0alpha2AppsTobeta1.html | 0 3 files changed, 84 insertions(+), 63 deletions(-) rename READMEconvertingR3.14.0alpha2AppsToalpha3.html => READMEconvertingR3.14.0alpha2AppsTobeta1.html (100%) diff --git a/README b/README index 90b9f8be0..6ae191370 100644 --- a/README +++ b/README @@ -274,20 +274,29 @@ Building EPICS base (Unix and Win32) Set environment variable + Files in the base/startup directory have been provided to help + set required path and other environment variables . + + EPICS_HOST_ARCH Before you can build or use EPICS R3.14, the environment variable EPICS_HOST_ARCH must be defined. A perl script EpicsHostArch.pl in the base/startup directory has been provided to help set EPICS_HOST_ARCH. You should have EPICS_HOST_ARCH set to your host operating system followed by a dash and then your host architecture, - e.g. solaris-sparc. + e.g. solaris-sparc. If you are not using the OS vendor's + c/c++ compiler for host builds, you will need another dash + followed by the alternate compiler name (e.g. "-gnu" for GNU + c/c++ compilers on a solaris host or "-borland" for Borland + c/c++ compilers on a WIN32 host) . See configure/CONFIG_SITE + for a list of supported EPICS_HOST_ARCH values. + PERLLIB On WIN32, some versions of Perl require that the environment variable PERLLIB be set to . - Check path requirements - + PATH As already mentioned, you must have the perl executable and you may need C and C++ compilers in your search path. For building base you also must have echo in your search @@ -296,16 +305,19 @@ Building EPICS base (Unix and Win32) exist. On some Unix systems you may also need ar and ranlib in your path, and the c compiler may require ld in your path. + Unix LD_LIBRARY_PATH If you plan to build EPICS base shared libraries instead of archive libraries, on Unix systems you will need to add fullpathname to $(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) to - your LD_LIBRARY_PATH environment variable. On - WIN32 systems, building shared libraries is the default + your LD_LIBRARY_PATH environment variable. + + Win32 PATH + On WIN32 systems, building shared libraries is the default setting and you will need to add fullpathname to - $(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) to - your path. Building shared libraries is determined by the - value of the macro SHARED_LIBRARIES in - CONFIG_SITE (either YES or NO). + $(INSTALL_LOCATION)/bin/$(EPICS_HOST_ARCH) to your path. + Building shared libraries is determined by the value of the + macro SHARED_LIBRARIES in CONFIG_SITE (either YES or NO). + Do site-specific build configuration @@ -317,7 +329,6 @@ Building EPICS base (Unix and Win32) configure/CONFIG_SITE_ENV Environment variable defaults configure/RELEASE TORNADO 2 full path location - Host configuration To configure each host system, you may override the default definitions by adding a new file with override definitions into @@ -341,9 +352,9 @@ Building EPICS base (Unix and Win32) R3.13 compatibility configuration To configure EPICS base for building with R3.13 extensions - and ioc applications , you must modify the default definitions - in the base/config/CONFIG_SITE* files to agree with the - definitions in your base/configure files. + and ioc applications, you must modify the default definitions + in the base/config/CONFIG_SITE* files to agree with definitions + you made in base/configure and base/configure/os files. Build EPICS base @@ -369,22 +380,22 @@ Multiple host platforms systems and for multiple cross target systems. The intermediate and binary files generated by the build will be created in separate subdirectories and installed into the appropriate separate host/target - install directories. EPICS executables and perl scripts are installed into - the $(INSTALL_LOCATION)/bin/ directories. Libraries are + install directories. EPICS executables and perl scripts are installed + into the $(INSTALL_LOCATION)/bin/ directories. Libraries are installed into $(INSTALL_LOCATION)/lib/. The default definition for $(INSTALL_LOCATION) is $(TOP) which is the root directory in the distribution directory structure, base. Created object files are stored in O. source subdirectories, This allows objects for multiple cross target architectures to be maintained at the same time. To build EPICS base for a specific host/target combination you - must have the proper host/target c++ cross compiler and target header + must have the proper host/target c/c++ cross compiler and target header files and the base/configure/os directory must have the appropriate configure files. Example application and extension A perl tool, makeBaseApp.pl is included in the distribution file. This - script will create a sample application that then can be built and then + script will create a sample application that can be built and then executed to try out this release of base. Also, 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 @@ -394,7 +405,7 @@ Example application and extension Instructions for building and executing the 3.14 example application can be found in the section "Example Application" of Chapter 2, "New Features for 3.14", in the "IOC Application Developer's Guide - R3.14.0beta1" . The "Example Application" section briefly explains + R3.14.0beta1". The "Example Application" section briefly explains how to create and build an example application in a user created directory. It also explains how to run the example application on a vxWorks ioc or a host system and run an example channel access client diff --git a/README.htm b/README.htm index 344665669..ea1dbcc2d 100644 --- a/README.htm +++ b/README.htm @@ -17,7 +17,7 @@ EPICS base

-Release 3.14.0alpha3

+Release 3.14.0beta1

What is EPICS base?

@@ -75,6 +75,7 @@ Cross compile target platforms (operating system - architecture)
vxWorks-68040
vxWorks-68040lc
vxWorks-68060 +
vxWorks-ppc603
vxWorks-ppc604
vxWorks-pentium
RTEMS-gen68360 @@ -115,12 +116,9 @@ file. You will also need one or more board support packages. Consult the vxWorks documentation for details.

Optional GNU compiler requirement for solaris-sparc  and win32-x86 hosts -
If you wish to have the build automatically  create header dependancy -include files for c/c++ source code (HDEPENDS set to YES in CONFIG_SITE) -, the gnu compilers gcc and  g++ must be be in your path. Also, if -you have state notation language source files (*.st files) which require -c preprocessing before conversion to c source,  gcc must be in your -path. +
If you have state notation language source files (*.st files) which +require c preprocessing before conversion to c source,  gcc must be +in your path.

Host system storage requirements

@@ -414,28 +412,41 @@ Building EPICS base (Unix and Win32)
Unpack file
Unzip and untar the distribution file. Use WinZip on Windows systems.
-Set environment variable -
Before you can build or use EPICS R3.14, the environment variable -EPICS_HOST_ARCH must be defined. A perl script EpicsHostArch.pl in the -base/startup directory has been provided to help set EPICS_HOST_ARCH. You -should have EPICS_HOST_ARCH set to your host operating system followed -by a dash and then your host architecture, e.g. solaris-sparc. -

On WIN32, some versions of Perl require that  the environment variable -PERLLIB be set to <perl directory location>.

-Check path requirements -
As already mentioned, you must have the perl executable and -you may need C and C++ compilers in your search path. For building base -you also must have echo in your search path. For Unix host builds you also -need touch, cpp, cp, rm, mv, and mkdir in your search path and /bin/chmod -must exist. On some Unix systems you may also need ar and ranlib in your -path, and the c compiler may require ld in your path. -

If you plan to build EPICS base shared libraries instead of archive +Set environment variables +

Files in the base/startup directory have been provided to help +set required path and other environment variables . +

EPICS_HOST_ARCH +
Before you can build or use EPICS R3.14, the environment variable EPICS_HOST_ARCH +must be defined. A perl script EpicsHostArch.pl in the base/startup directory +has been provided to help set EPICS_HOST_ARCH. You should have EPICS_HOST_ARCH +set to your host operating system followed by a dash and then your host +architecture, e.g. solaris-sparc. If you are not using the OS vendor's +c/c++ compiler for host +
builds, you will need another dash followed by the alternate compiler +name (e.g. "-gnu" for GNU c/c++ compilers on a solaris host or "-borland" +for Borland c/c++ compilers on a WIN32 host) .  See configure/CONFIG_SITE +for a list of supported EPICS_HOST_ARCH values. +

PERLLIB +
On WIN32, some versions of Perl require that  the environment +variable PERLLIB be set to <perl directory location>.

+ +
PATH +
As already mentioned, you must have the perl executable and you may +need C and C++ compilers in your search path. For building base you also +must have echo in your search path. For Unix host builds you also need +touch, cpp, cp, rm, mv, and mkdir in your search path and /bin/chmod must +exist. On some Unix systems you may also need ar and ranlib in your path, +and the c compiler may require ld in your path. +

LD_LIBRARY_PATH +
If you plan to build EPICS base shared libraries instead of archive libraries, on Unix systems you will need to add  fullpathname to $(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) -to your LD_LIBRARY_PATH environment variable. On WIN32 systems, building -shared libraries is the default setting and you will need to add  -fullpathname to $(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) to your path. -Building shared libraries is determined by the value of the macro SHARED_LIBRARIES -in CONFIG_SITE (either YES or NO).

+to your LD_LIBRARY_PATH environment variable. +

PATH +
On WIN32 systems, building shared libraries is the default setting +and you will need to add  fullpathname to $(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) +to your path. Building shared libraries is determined by the value of the +macro SHARED_LIBRARIES in CONFIG_SITE (either YES or NO). +
 

Do site-specific build configuration
Site configuration
To configure EPICS, you may want to modify the default definitions @@ -443,11 +454,9 @@ in the following files:
configure/CONFIG_SITE     Build choices. Specify target archs.
configure/CONFIG_SITE_ENV Environment variable  defaults -
configure/RELEASE        -TORNADO +
configure/RELEASE        TORNADO 2 full path location
- -


Host configuration +Host configuration
To configure each host system, you may override the default definitions by adding a new file with override definitions into the configure/os directory. The new file should have the same name as the distribution file to be overridden @@ -468,7 +477,8 @@ settings

R3.13 compatibility configuration
To configure EPICS base for building with R3.13 extensions and ioc applications , you must modify the default definitions in the base/config/CONFIG_SITE*  -files to agree with the definitions in your base/configure files.
+files to agree with definitions you made in base/configure and base/configure/os +files.

Build EPICS base

@@ -500,7 +510,7 @@ which is the root directory in the distribution directory structure, base. Created object files are stored in O.<arch> source subdirectories, This allows objects for multiple cross target architectures to be maintained at the same time. To build EPICS base for a specific host/target combination -you must have the proper host/target c++ cross compiler and target header +you must have the proper host/target c/c++ cross compiler and target header files and the base/configure/os directory must have the appropriate configure files. @@ -508,20 +518,20 @@ files. Example application and extension
A perl tool, makeBaseApp.pl is included in the distribution -file. This script will create a sample application that then can be built -and then executed to try out this release of base. Also, 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/<hostarch> -directory during the base build.
+file. This script will create a sample application that can be built and +then executed to try out this release of base. Also, 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/<hostarch> directory +during the base build.
Instructions for building and executing the 3.14 example application can be found in the section "Example Application" of Chapter 2, "New Features -for 3.14", in the  "IOC Application Developer's Guide R3.14.0alpha3" -. The "Example Application"  section briefly explains how to create -and build an example application in a user created <top> directory. -It also explains how to run the example application on a vxWorks ioc or -a host system and run an example channel access client on the host system.
+for 3.14", in the  "IOC Application Developer's Guide R3.14.0beta1". +The "Example Application" section briefly explains how to create and build +an example application in a user created <top> directory. It also explains +how to run the example application on a vxWorks ioc or a host system and +run an example channel access client on the host system. diff --git a/READMEconvertingR3.14.0alpha2AppsToalpha3.html b/READMEconvertingR3.14.0alpha2AppsTobeta1.html similarity index 100% rename from READMEconvertingR3.14.0alpha2AppsToalpha3.html rename to READMEconvertingR3.14.0alpha2AppsTobeta1.html