GNU make -
You must use GNU make, gnumake, for any EPICS builds. Set your +
You must use GNU make, gnumake, for any EPICS builds. Set your path so that a gnumake version 3.78.1 or later is available.Perl
You must have perl version 5.0 or later installed. The configure files -do not specify the perl full pathname. You need the perl executable +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.Tornado 2.0
You must have Tornado 2.0 installed if any of your target systems are -vxWorks systems. Tornado 2.0 provides the cross-compiler and header +vxWorks systems. Tornado 2.0 provides the cross-compiler and header files needed to build for these target systems. The full path location to Tornado 2.0 must 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. -Optional GNU compiler requirement for solaris-sparc and win32-x86 +
Optional GNU compiler requirement for solaris-sparc and win32-x86 hosts
If you have state notation language source files (*.st files) which -require c preprocessing before conversion to c source, gcc must be +require c preprocessing before conversion to c source, gcc must be in your path.
EPICS documentation is available on the WWW via the EPICS home -page at APS: URL http://www.aps.anl.gov/epics+page at APS: URL http://www.aps.anl.gov/epics
This README.html is in the base distribution file and will be available on the IOC software R3.14 EPICS WWW page which can be accessed @@ -155,11 +155,11 @@ Other WWW sites other WWW links on the EPICS home page at APS.
There are five EPICS mailing lists provided by APS. See The -EPICS home page for subscription instructions.- +
There is an EPICS mailing list called tech-talk which is hosted at +APS with a list repeater at BESSY. See The EPICS home page for subscription +instructions.
PERLLIB
-
On WIN32, some versions of Perl require that the environment
+
On WIN32, some versions of Perl require that the environment
variable PERLLIB be set to <perl directory location>.
PATH @@ -443,11 +443,11 @@ 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.@@ -480,7 +480,7 @@ except with CONFIG in the name replaced by CONFIG_SITE. settings R3.13 compatibility configurationLD_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) +libraries, on Unix systems you will need to add fullpathname to $(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) 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) +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).
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.0beta2". +for 3.14", in the "IOC Application Developer's Guide R3.14.0beta2". 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