diff --git a/README.htm b/README.htm index 96303d343..5f8ffc15b 100644 --- a/README.htm +++ b/README.htm @@ -49,15 +49,15 @@ for legal terms of usage. Supported platforms
Currently this version of EPICS base has been built on the -following hosts and targets. If you are trying to build EPICS base on a -different host or for a different target machine you must have the proper -host/target cross compiler and header files and you will have to add the -appropriate configure files to 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.+following hosts for the following targets. If you are trying to build EPICS +base on a different host or for a different target machine you must get +the proper host/target cross compiler and header files and you will have +to create and add the appropriate new configure files to 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 target platforms (operating system - architecture - -<alternate c++ compiler>) ++by a dash and then your host architecture, e.g. solaris-sparc. +Host platforms (operating system - architecture - <alternate +c++ compiler>)solaris-sparc+
solaris-sparc-gnu
linux-x86 @@ -113,13 +113,13 @@ 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. -GNU compiler for solaris-sparc and win32-x86 hosts -
The host architecture build requires that g++ be in your path if you -wish to run "gnumake depends" (not required) to create header dependancy -include files for c/c++ source code. Also, if you have state notation language -source files which require c preprocessing to generate solaris-sparc object -files (*.st files), gcc must be in your path. -
Optional GNU compiler requirement for solaris-sparc and win32-x86 +hosts +
If you wish to run "gnumake depends" to create header dependancy +include files for c/c++ source code, 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.Host system storage requirements
@@ -278,7 +278,7 @@ Build related componentsbase/README* files -
README.htm +
README.htm Instructions for setup and building epics base
(i.e. this document) @@ -292,7 +292,7 @@ instructionsbase/startup directory - contains scripts to set environment and path -
EpicsHostArch c shell script +
EpicsHostArch c shell script to set EPICS_HOST_ARCH env variable
EpicsHostArch.pl perl script to set EPICS_HOST_ARCH env variable @@ -308,9 +308,7 @@ WIN32 bat file to set path and env variablesbase/configure directory - contains build definitions and rules -
--
CONFIG.CrossCommon Cross build definitions +
CONFIG.CrossCommon Cross build definitions
CONFIG_ADDONS Definitions for <osclass> and DEFAULT options
CONFIG_BASE @@ -347,9 +345,7 @@ Rules specific to a <top> dir (uninstall and tar)base/configure/os directory - contains os-arch specific definitions -
--
CONFIG.<host>.<target> Specific +
CONFIG.<host>.<target> Specific host-target build definitions
CONFIG.Common.<target> Specific target definitions for all hosts @@ -365,9 +361,7 @@ R3.13 arch compatibility definitionsbase/configure/tools directory - contains Perl scripts used for the build -
--
cp.pl +
cp.pl This Perl script copies an existing file
installEpics.pl Installs built files into install directories. @@ -401,14 +395,23 @@ Set 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 you -path, and the c compiler may require ld in your path..+path, and the c compiler may require ld in your 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 (YES or NO). Do site-specific build configuration
Site configurationR3.13 compatibility configuration
To configure EPICS, you may want to modify the default definitions @@ -441,7 +444,7 @@ settings
iocCore is now supported on the following platforms: +EPICS Release base 3.14.0alpha2 + +
http://www.aps.anl.gov/epics/modules/base/R3-14.php -
Most of the Application Developer's Guide has only minor changes. The -following are new. +
It must be emphasized that this is an alpha release.
change INSTALLDB to +DB +
change DBDINSTALL to
+DBD
+
+