epics/pcas
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

Minor edits; mainly that tech-talk is now the only EPICS mailing list we ever

Browse Source 
talk about in public.
This commit is contained in:
Andrew Johnson
2002-08-21 22:21:15 +00:00
parent 2bb26522e0
commit 0058debd45
2 changed files with 21 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/README.1st
+4 -3
View File
@@ -114,7 +114,7 @@ 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
page at APS: URL http://www.aps.anl.gov/epics
This README.1st is in the base distribution file and will be available
on the IOC software R3.14 EPICS WWW page which can be accessed
@@ -133,8 +133,9 @@ WWW pages
Mailing Lists
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.
Directory Structure
documentation/README.html
+17 -17
View File
@@ -99,26 +99,26 @@ in CONFIG_SITE.</blockquote>
Software requirements</h3>
<blockquote><b>GNU make</b>
<br>You must use GNU make, gnumake, for any EPICS builds.&nbsp; Set your
<br>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.
<p><b>Perl</b>
<br>You must have perl version 5.0 or later installed. The configure files
do not specify the perl full pathname.&nbsp; You need the perl executable
do not specify the perl full pathname. You need the perl executable
in your search path.
<p><b>Unzip and tar (Winzip on WIN32 systems)</b>
<br>You must have tools available to unzip and untar the EPICS base distribution
file.
<p><b>Tornado 2.0</b>
<br>You must have Tornado 2.0 installed if any of your target systems are
vxWorks systems.&nbsp; 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.&lt;hostarch>
file. You will also need one or more board support packages. Consult the
vxWorks documentation for details.
<p><b>Optional GNU compiler requirement for solaris-sparc&nbsp; and win32-x86
<p><b>Optional GNU compiler requirement for solaris-sparc and win32-x86
hosts</b>
<br>If you have state notation language source files (*.st files) which
require c preprocessing before conversion to c source,&nbsp; gcc must be
require c preprocessing before conversion to c source, gcc must be
in your path.</blockquote>
<h3>
@@ -133,7 +133,7 @@ files for each target take approximately 10 MB.</blockquote>
Documentation</h3>
<blockquote>EPICS documentation is available on the WWW via the EPICS home
page at APS:&nbsp; URL <a href="http://www.aps.anl.gov/epics">http://www.aps.anl.gov/epics</a></blockquote>
page at APS: URL <a href="http://www.aps.anl.gov/epics">http://www.aps.anl.gov/epics</a></blockquote>
<blockquote>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</h4>
other WWW links on the EPICS home page at APS.</blockquote>
<h4>
Mailing Lists</h4>
Mailing List</h4>
<blockquote>There are five EPICS mailing lists provided by APS. See The
EPICS home page for subscription instructions.</blockquote>
</blockquote>
<blockquote>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.</blockquote> </blockquote>
<h3>
Directory Structure</h3>
@@ -428,10 +428,10 @@ architecture, e.g. solaris-sparc. If you are not using the OS vendor's
c/c++ compiler for host
<br>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) .&nbsp; See configure/CONFIG_SITE
for Borland c/c++ compilers on a WIN32 host). See configure/CONFIG_SITE
for a list of supported EPICS_HOST_ARCH values.
<p><b>PERLLIB</b>
<br>On WIN32, some versions of Perl require that&nbsp; the environment
<br>On WIN32, some versions of Perl require that the environment
variable PERLLIB be set to &lt;perl directory location>.</blockquote>
<blockquote><b>PATH</b>
@@ -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.
<p><b>LD_LIBRARY_PATH</b>
<br>If you plan to build EPICS base shared libraries instead of archive
libraries, on Unix systems you will need to add&nbsp; 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.
<p><b>PATH</b>
<br>On WIN32 systems, building shared libraries is the default setting
and you will need to add&nbsp; 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).
<br>&nbsp;</blockquote>
@@ -480,7 +480,7 @@ except with CONFIG in the name replaced by CONFIG_SITE.
settings</blockquote>
<b>R3.13 compatibility configuration</b>
<br>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*&nbsp;
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.</blockquote>
@@ -496,7 +496,7 @@ The command "gnumake clean uninstall" will remove all files and directories
generated by a previous build. The command "gnumake" will build and install
everything for the configured host and targets.
<br>It is recommended that you do a "gnumake clean uninstall" at the root
directory of an EPICS&nbsp; directory structure before each complete rebuild
directory of an EPICS directory structure before each complete rebuild
to ensure that all components will be rebuilt.</blockquote>
</blockquote>
@@ -531,7 +531,7 @@ during the base build.</blockquote>
<blockquote>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&nbsp; "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 &lt;top> directory. It also explains
how to run the example application on a vxWorks ioc or a host system and