documentation: Various updates...
Removed the Converting... files for older releases No known problems yet. Updated README.html and regenerated README.1st from it. Added windows-x64 target to the Release notes.
This commit is contained in:
Andrew Johnson
@@ -1,145 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>
|
||||
Converting an EPICS R3.14.0 alpha2 application to beta1</h2></center>
|
||||
|
||||
<p><br>This document describes how to convert a R3.14.0alpha2 application
|
||||
so that it builds with release R3.14.0beta1.
|
||||
<h3>
|
||||
Gnumake clean uninstall</h3>
|
||||
|
||||
<blockquote>First do a "<tt>gnumake clean uninstall"</tt> in the application's
|
||||
root directory to remove all files created by earlier builds.</blockquote>
|
||||
|
||||
<h3>
|
||||
Replace configure/RULES.ioc and configure/Makefile</h3>
|
||||
|
||||
<blockquote>The rules defined in RULES.ioc have changed slightly, and new
|
||||
applications are now given a wrapper version which just includes $(EPICS_BASE)/configure/RULES.ioc.
|
||||
The new configure/Makefile contains an additional macro that causes the
|
||||
contents of the configure/RELEASE file to be checked at build time for
|
||||
consistency with all the support applications that it references. These
|
||||
files should be replaced with copies of the new versions from <base>/templates/makeBaseApp/top/configure</blockquote>
|
||||
|
||||
<h3>
|
||||
Remove baseLIBOBJS</h3>
|
||||
|
||||
<blockquote>Record and device support from base now exists in archive libraries
|
||||
so baseLIBOBJS is no longer needed and the file and references to it in
|
||||
the Makefile can be deleted. e.g. remove
|
||||
<blockquote><tt>-include ../baseLIBOBJS</tt></blockquote>
|
||||
and the file baseLIBOBJS. If there are no LIBOBJS definitions in the Makefile,
|
||||
also remove
|
||||
<blockquote><tt>example_OBJS += $(LIBOBJS)</tt></blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3>
|
||||
Libraries recIoc, softDevIoc, and testDevIoc</h3>
|
||||
|
||||
<blockquote>Add the new record and dev support libraries to <name>App/src/Makefile,
|
||||
i.e. add the lines
|
||||
<blockquote><tt>example_LIBS += recIoc</tt>
|
||||
<br><tt>example_LIBS += softDevIoc</tt>
|
||||
<br><tt>example_LIBS += testDevIoc</tt></blockquote>
|
||||
and remove any references to iocLibrary, e.g. remove the line
|
||||
<blockquote><tt>example_OBJS_vxWorks += $(EPICS_BASE_BIN)/iocCoreLibrary</tt></blockquote>
|
||||
The order of references to base libraries is important so place recIoc
|
||||
and softDevIoc before the the other base library references.
|
||||
<p>If you are building on a WIN32 host add the following lines instead:
|
||||
<blockquote><tt># Use win32 object libs for registered support</tt>
|
||||
<br><tt>example_LIBS_win32 += recIocObj</tt>
|
||||
<br><tt>example_LIBS_win32 += softDevIocObj</tt>
|
||||
<br><tt>example_LIBS_win32 += testDevIocObj</tt>
|
||||
<br><tt>example_LIBS_DEFAULT += recIoc</tt>
|
||||
<br><tt>example_LIBS_DEFAULT += softDevIoc</tt>
|
||||
<br><tt>example_LIBS_DEFAULT += testDevIoc</tt></blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3>
|
||||
iocrf renamed to iocsh</h3>
|
||||
|
||||
<blockquote>Change all references to ioccrf in your application src directories
|
||||
to iocsh e.g.
|
||||
<p>change <tt>#include "ioccrf.h"</tt>
|
||||
<br>to <tt>#include "iocsh.h"</tt>
|
||||
<p>change<tt> ioccrf(argv[1]);</tt>
|
||||
<br>to <tt> iocsh(argv[1]);</tt>
|
||||
<p>and change <tt> ioccrf(NULL);</tt>
|
||||
<br>to <tt>iocsh(NULL)</tt>;
|
||||
<p>in <name>App/src/exampleMain.c.</blockquote>
|
||||
|
||||
<h3>
|
||||
PROD changes</h3>
|
||||
|
||||
<blockquote>PROD targets will now be built for all target architectures.
|
||||
If a product should be built only for host architectures change PROD to
|
||||
PROD_HOST .e.g. in your application src Makefiles
|
||||
<blockquote>change <tt>PROD += caExample</tt>
|
||||
<br>to <tt>PROD_HOST += caExample</tt>
|
||||
<br>and
|
||||
<br>change <tt>PROD = sncExample</tt>
|
||||
<br>to <tt>PROD_HOST += sncExample</tt></blockquote>
|
||||
</blockquote>
|
||||
<b>LIBRARY and PROD changes</b>
|
||||
<blockquote>The meaning of LIBRARY and PROD have now changed. For vxWorks,
|
||||
LIBRARY now means an archive library, OBJLIB is now a combined object file
|
||||
(only needed for R3.13 compatibility) and PROD is now a combined object
|
||||
file with library references resolved and will have a corresponding .munch
|
||||
file created. Thus, in your application src Makefiles,
|
||||
<blockquote>change <tt>LIBRARY_vxWorks = <name></tt>
|
||||
<br>to <tt>PROD_vxWorks = <name></tt>
|
||||
<br>or
|
||||
<br>remove the lines <tt>LIBRARY_vxWorks = <name></tt>
|
||||
<br>and <tt>PROD_RTEMS = <name></tt>
|
||||
<br>and change <tt>PROD = <name></tt>
|
||||
<br>to <tt>PROD_IOC = <name></tt>.</blockquote>
|
||||
In the iocBoot/ioc<name>/st.cmd files,
|
||||
<blockquote>change <tt>ld < <name>Library.munch</tt>
|
||||
<br>to <tt>ld < <name>.munch</tt></blockquote>
|
||||
A SRCS definition is now required for every PROD and LIBRARY source
|
||||
file to determine correct header file dependancies. This is true even if
|
||||
there is only one source file for the PROD or LIBRARY . Thus, for the PROD
|
||||
caExample in your src Makefile, add the line
|
||||
<blockquote> caExample_SRCS += caExample.c</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3>
|
||||
registerRecordDeviceDriver changes</h3>
|
||||
|
||||
<blockquote>The created file registerRecordDeviceDriver.cpp is now used
|
||||
for all target architectures. Thus in your application src Makefiles
|
||||
<blockquote>change <tt>example_SRCS_DEFAULT += example_registerRecordDeviceDriver.cpp</tt>
|
||||
<br>to <tt>example_SRCS += example_registerRecordDeviceDriver.cpp</tt>
|
||||
<br><tt></tt> </blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3>
|
||||
RTEMS-specific pathname changes</h3>
|
||||
|
||||
<blockquote>1. The RTEMS TFTP remote filesystem no longer ignores leading
|
||||
`../' components in path names. All st.cmd file lines with path names
|
||||
of the form <tt>dbLoadRecords("../../db/dbExample1.db","user=norume")</tt>
|
||||
<br>must be changed to
|
||||
<br><tt>dbLoadRecords("db/dbExample1.db","user=norume")</tt><tt></tt>
|
||||
<p>The makeBaseApp.pl script distributed with R3.14-beta1 creates st.cmd
|
||||
scripts with the proper path names.
|
||||
<p>2. The RTEMS TFTP remote filesystem supports a limited set of chdir
|
||||
operations.
|
||||
<br>All paths passed to chdir (or to the IOC shell `cd' command) must end
|
||||
in a `/'
|
||||
<br>character.</blockquote>
|
||||
|
||||
<blockquote>
|
||||
<blockquote> </blockquote>
|
||||
</blockquote>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,30 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2> Converting an EPICS R3.14.0 beta1 application to beta2</h2></center>
|
||||
|
||||
<p><br>This document describes how to convert a R3.14.0beta1 application
|
||||
so that it builds with release R3.14.0beta2.
|
||||
|
||||
<h3>Update Unix LD_LIBRARY_PATH</h3>
|
||||
|
||||
If you build EPICS base shared libraries instead of archive
|
||||
libraries on Unix systems you will need to update your
|
||||
LD_LIBRARY_PATH environment variable to include fullpathname
|
||||
to the NEW base $(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH).
|
||||
|
||||
<h3>Update Win32 PATH</h3>
|
||||
|
||||
On WIN32 systems, building shared libraries is the default
|
||||
setting so, unless SHARED_LIBRARIES was changed to NO, you will
|
||||
need to update your path to include fullpathname to the NEW
|
||||
base $(INSTALL_LOCATION)/bin/$(EPICS_HOST_ARCH).
|
||||
|
||||
</html>
|
||||
@@ -1,15 +0,0 @@
|
||||
<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]"></head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2> Converting an EPICS R3.14.0 beta2 application to R3.14.1</h2></center>
|
||||
|
||||
<p><br>This document describes how to convert a R3.14.0beta2 application
|
||||
so that it builds with release R3.14.1.
|
||||
|
||||
</p><h3>No changes required.</h3>
|
||||
|
||||
@@ -1,243 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
||||
"http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>Converting an EPICS R3.14.1 application to R3.14.2</h2>
|
||||
</center>
|
||||
|
||||
<p>This document describes how to convert a R3.14.1 application so that it
|
||||
builds with release R3.14.2.</p>
|
||||
|
||||
<p><span style="font-weight: bold">MAJOR CHANGE since 3.14.1</span></p>
|
||||
|
||||
<p>The base supplied record and device support are now build as regular
|
||||
libraries rather than as just object files. This allows simplified build
|
||||
ruiles. The changes do require changes to:</p>
|
||||
<ul>
|
||||
<li>any record, device, or driver support you provide.</li>
|
||||
<li>changes to any subroutines for subRecord.</li>
|
||||
<li>replace any DBD <span style="font-family: courier">function</span>
|
||||
statements with <span style="font-family: courier">register</span>
|
||||
statements</li>
|
||||
</ul>
|
||||
|
||||
<p>Please read the new chapter "Getting Started" of the Application
|
||||
Developer's Guide for more information about building support and ioc
|
||||
applications.</p>
|
||||
|
||||
<h3>Gnumake clean uninstall</h3>
|
||||
|
||||
<blockquote>
|
||||
First do a "<tt>gnumake clean uninstall"</tt> in the application's root
|
||||
directory to remove all files created by earlier builds.</blockquote>
|
||||
|
||||
<h3>INSTALL_LOCATION_APP</h3>
|
||||
|
||||
<blockquote>
|
||||
If your application is NOT being installed into $(TOP), move your
|
||||
INSTALL_LOCATION_APP definition to the configure/RELEASE file.</blockquote>
|
||||
|
||||
<h3>Building db files from templates changed</h3>
|
||||
|
||||
<blockquote>
|
||||
Now if the template needed to build <name>.db is not named
|
||||
<name>*.template add the line
|
||||
|
||||
<blockquote>
|
||||
<pre> <name>_template = <templatename></pre>
|
||||
</blockquote>
|
||||
to the *Db/Makefile.
|
||||
|
||||
<p>Remove any</p>
|
||||
|
||||
<blockquote>
|
||||
<pre>USES_TEMPLATE =</pre>
|
||||
</blockquote>
|
||||
definitions from your <name>App/*Db/Makefile files; these definitions
|
||||
are no longer used.</blockquote>
|
||||
|
||||
<h3>File base.dbd no longer needed</h3>
|
||||
|
||||
<blockquote>
|
||||
You now can add the line include "base.dbd" to your
|
||||
<appname>Include.dbd file and remove the file
|
||||
<name>App/src/base.dbd from your src directory. The base.dbd from
|
||||
R3.14.2 base/dbd will be included. However, if you only want a subset of
|
||||
record definitions from base you should keep your base.dbd
|
||||
file.</blockquote>
|
||||
|
||||
<h3>Record support</h3>
|
||||
|
||||
<blockquote>
|
||||
Add the following line after all existing #includes
|
||||
|
||||
<blockquote>
|
||||
<pre>#include "epicsExport.h"</pre>
|
||||
</blockquote>
|
||||
The structure rset is now a typedef so change
|
||||
|
||||
<blockquote>
|
||||
<pre>struct rset <recordname>RSET={ ...</pre>
|
||||
</blockquote>
|
||||
to
|
||||
|
||||
<blockquote>
|
||||
<pre>rset <recordname>RSET={ ...</pre>
|
||||
</blockquote>
|
||||
and add the following line after the "rset <recordname>RSET="
|
||||
definition.
|
||||
|
||||
<blockquote>
|
||||
<pre>epicsExportAddress(rset,xxxRSET);</pre>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3>Device support</h3>
|
||||
|
||||
<blockquote>
|
||||
Add the following line after all existing #includes
|
||||
|
||||
<blockquote>
|
||||
<pre>#include "epicsExport.h"</pre>
|
||||
</blockquote>
|
||||
and add the following line after the dset dev<devname> definition
|
||||
|
||||
<blockquote>
|
||||
<pre>epicsExportAddress(dset,dev<devname>);</pre>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3>Driver support</h3>
|
||||
|
||||
<blockquote>
|
||||
Add the following line after all existing #includes
|
||||
|
||||
<blockquote>
|
||||
<pre>#include "epicsExport.h"</pre>
|
||||
</blockquote>
|
||||
and add the following line after the drvet dev<devname> definition
|
||||
|
||||
<blockquote>
|
||||
<pre>epicsExportAddress(drvet,drv<devname>);</pre>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3>Registration code changed</h3>
|
||||
|
||||
<blockquote>
|
||||
Registration code for application specific functions, e.g. subroutine
|
||||
record init and process functions, has been changed as follows
|
||||
|
||||
<p>1) Include the registration support header files:</p>
|
||||
|
||||
<blockquote>
|
||||
<pre>#include "dbDefs.h"
|
||||
#include "registryFunction.h"</pre>
|
||||
</blockquote>
|
||||
2) Include the export definitions header file after including all other
|
||||
header files:
|
||||
|
||||
<blockquote>
|
||||
<pre>#include "epicsExport.h"</pre>
|
||||
</blockquote>
|
||||
3) Make the application specific functions static functions, e.g.
|
||||
|
||||
<blockquote>
|
||||
<pre>static long mySubInit(subRecord *precord,processMethod process)
|
||||
static long mySubProcess(subRecord *precord)</pre>
|
||||
</blockquote>
|
||||
4) Define a registryFunctionRef array of the application specific functions
|
||||
to be registered, e.g.
|
||||
|
||||
<blockquote>
|
||||
<pre>static registryFunctionRef mySubRef[] = {
|
||||
{"mySubInit",(REGISTRYFUNCTION)mySubInit},
|
||||
{"mySubProcess",(REGISTRYFUNCTION)mySubProcess}
|
||||
};</pre>
|
||||
</blockquote>
|
||||
5) Add a new function to do the registration of the registryFunctionRef
|
||||
array elements, e.g.
|
||||
|
||||
<blockquote>
|
||||
<pre>void mySub(void)
|
||||
{
|
||||
registryFunctionRefAdd(mySubRef,NELEMENTS(mySubRef));
|
||||
}</pre>
|
||||
</blockquote>
|
||||
6) Call the epicsExportRegistrar with the new registration function: e.g.
|
||||
|
||||
<blockquote>
|
||||
<pre>epicsExportRegistrar(mySub);</pre>
|
||||
</blockquote>
|
||||
7) Remove the existing function lines in <appname>Include.dbd: e.g.
|
||||
remove
|
||||
|
||||
<blockquote>
|
||||
<pre>function("mySubInit")
|
||||
function("mySubProcess")</pre>
|
||||
</blockquote>
|
||||
8) Add a registrar statement to <name>Include.dbd with the new
|
||||
registration function as parameter: e.g. add
|
||||
|
||||
<blockquote>
|
||||
<pre>registrar("mySub")</pre>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
<h3><name>App/src/Makefile changed and simplified</h3>
|
||||
|
||||
<blockquote>
|
||||
1) Libraries from support modules defined in configure/RELEASE no longer
|
||||
need the <libname>_DIR definitions. You can remove lines like the
|
||||
following from your src/Makefile
|
||||
|
||||
<blockquote>
|
||||
<pre>ca_DIR = $(EPICS_BASE_LIB)
|
||||
Com_DIR = $(EPICS_BASE_LIB)</pre>
|
||||
</blockquote>
|
||||
2) Libraries from EPICS_BASE do not have to be specified individually. For
|
||||
HOST products and libraries specify the following
|
||||
|
||||
<blockquote>
|
||||
<pre><myhostprodorlib>_LIBS += $(EPICS_BASE_HOST_LIBS)</pre>
|
||||
</blockquote>
|
||||
For IOC products and libraries specify the following
|
||||
|
||||
<blockquote>
|
||||
<pre><myiocprodorlib>_LIBS += $(EPICS_BASE_IOC_LIBS)</pre>
|
||||
</blockquote>
|
||||
3) All record, device, and driver support must now exist in shared
|
||||
libraries. You will need to create an IOC library containing your
|
||||
application specific support.
|
||||
|
||||
<blockquote>
|
||||
<pre>LIBRARY_IOC += exampleIoc
|
||||
|
||||
exampleIoc_SRCS += xxxRecord.c
|
||||
exampleIoc_SRCS += devXxxSoft.c
|
||||
exampleIoc_SRCS += dbSubExample.c
|
||||
exampleIoc_LIBS += $(EPICS_BASE_IOC_LIBS)</pre>
|
||||
</blockquote>
|
||||
4) Add your new record, device, and driver support library to your ioc
|
||||
product's libraries: e.g.
|
||||
<pre>
|
||||
<blockquote>
|
||||
|
||||
PROD_IOC = example
|
||||
|
||||
example_LIBS += exampleIoc
|
||||
example_LIBS += $(EPICS_BASE_IOC_LIBS)</blockquote>
|
||||
|
||||
|
||||
</pre>
|
||||
</blockquote>
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,37 +0,0 @@
|
||||
<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]"></head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>Converting an EPICS R3.14.2 application to R3.14.3</h2></center>
|
||||
|
||||
<p>This document describes how to convert a R3.14.2 application
|
||||
so that it builds and runs properly with release R3.14.3.</p>
|
||||
|
||||
<h3>registerRecordDeviceDriver Name Change</h3>
|
||||
|
||||
<p>All application iocBoot/iocxxx/st.cmd files must be modified for R3.14.3 as
|
||||
the generated routine that registers record device and driver support has been
|
||||
renamed to incorporate the name of the dbd file it came from. The change to
|
||||
the startup script is straightforward; any pair of lines like this:</p>
|
||||
|
||||
<blockquote>
|
||||
<pre>dbLoadDatabase("dbd/<i>something</i>.dbd",0,0)
|
||||
registerRecordDeviceDriver(pdbbase)</pre>
|
||||
</blockquote>
|
||||
|
||||
<p>must have the second line changed so the result looks like this:</p>
|
||||
|
||||
<blockquote>
|
||||
<pre>dbLoadDatabase("dbd/<i>something</i>.dbd",0,0)
|
||||
<i>something</i>_registerRecordDeviceDriver(pdbbase)</pre>
|
||||
</blockquote>
|
||||
|
||||
<p>There may be other pathname components in the dbLoadDatabase line which
|
||||
should remain exactly as before.</p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,17 +0,0 @@
|
||||
<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]"></head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>Converting an EPICS R3.14.3 application to R3.14.4</h2></center>
|
||||
|
||||
<p>This document describes how to convert a R3.14.3 application
|
||||
so that it builds and runs properly with release R3.14.4.</p>
|
||||
|
||||
</p><h3>No changes required.</h3>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,17 +0,0 @@
|
||||
<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]"></head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>Converting an EPICS R3.14.4 application to R3.14.5</h2></center>
|
||||
|
||||
<p>This document describes how to convert a R3.14.4 application
|
||||
so that it builds and runs properly with release R3.14.5.</p>
|
||||
|
||||
</p><h3>No changes required.</h3>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,165 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
||||
"http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>Converting an EPICS R3.14.5 application to R3.14.6</h2>
|
||||
</center>
|
||||
|
||||
<p>This document describes how to convert a R3.14.5 application so that it
|
||||
builds with release R3.14.6.</p>
|
||||
|
||||
|
||||
<h3>Modify the Makefiles in <top>/iocBoot directory.</h3>
|
||||
|
||||
<p>Change " i<tt>nclude $(TOP)/config/CONFIG_APP" </tt>to "<tt>include
|
||||
$(TOP)/configure/CONFIG"</tt></p>
|
||||
|
||||
<p>If they do not already exist, add the lines
|
||||
<blockquote>
|
||||
<p><tt>DIRS += $(wildcard *ioc*)</tt></p>
|
||||
<p><tt>DIRS += $(wildcard as*)</tt></p>
|
||||
</blockquote>
|
||||
|
||||
<p>Change <tt>"include $(TOP)/config/RULES.iocBoot" </tt>to "i<tt>nclude
|
||||
$(TOP)/configure/RULES_DIRS"</tt></p>
|
||||
|
||||
<h3>Modify the Makefiles in <top>/iocBoot/ioc* directories.</h3>
|
||||
|
||||
<p>Change <tt>"include $(TOP)/config/CONFIG_APP" </tt>to "<tt>include
|
||||
$(TOP)/configure/CONFIG"</tt></p>
|
||||
|
||||
<p>Change</p>
|
||||
|
||||
<p><tt>ARCH = <old arch specification e.g. mv167></tt></p>
|
||||
|
||||
<p>to</p>
|
||||
|
||||
<p><tt>ARCH = <new arch specification e.g.
|
||||
vxWorks-68040></tt></p>
|
||||
|
||||
<p>Change "<tt>include $(TOP)/config/RULES.ioc</tt>" to "<tt>include
|
||||
$(TOP)/configure/RULES.ioc"</tt></p>
|
||||
|
||||
<p>If it exists remove the line</p>
|
||||
|
||||
<p><tt>buildInstall: cdCommands </tt></p>
|
||||
|
||||
<p>Add the line</p>
|
||||
<p><tt>TARGETS = cdCommands</tt></p>
|
||||
<p>before the include for RULES.ioc line.</p>
|
||||
|
||||
<h3>Modify st.cmd in <top>/iocBoot/ioc* directories.</h3>
|
||||
|
||||
<p>Remove the lines</p>
|
||||
<pre>ld < seq
|
||||
ld < iocCore</pre>
|
||||
|
||||
<p>Change "<tt>ld < <libname>Lib</tt>" to "<tt>ld <
|
||||
<libname>.munch"</tt></p>
|
||||
|
||||
<p>Change "<tt>cd appbin</tt>" to "<tt>cd topbin</tt>"</p>
|
||||
|
||||
<p>Change the statement:</p>
|
||||
|
||||
<p><tt>dbLoadDatabase("../../dbd/<name>App.dbd")</tt> <br>
|
||||
</p>
|
||||
to
|
||||
<pre>dbLoadDatabase("../../dbd/<name>.dbd")
|
||||
<name>_registerRecordDeviceDriver(pdbbase)</pre>
|
||||
|
||||
<p>where <name> is replaced with the name of your dbd file.</p>
|
||||
|
||||
<h3>recGbl calls</h3>
|
||||
|
||||
<p>If any source file makes calls to recGbl routines make sure it has <span
|
||||
style="font-family: courier">"#include "recGbl.h"</span>. If it doesn't the
|
||||
compiler will issue warning messages and the ioc may issue the message:
|
||||
"undefined symbol: _recGblSetSevr".</p>
|
||||
|
||||
<h3>Record support changes</h3>
|
||||
|
||||
<p>The steppermotor, scan, and pid records are no longer in base. If these
|
||||
records are not used in your application, comment out references to them in
|
||||
base.dbd. If these record types are used at your site, they should be
|
||||
downloaded and built with base R3.14 by your EPICS administrator. To update
|
||||
the R3.14 location of these record types in your application you must add
|
||||
appropriate module definitions to your application's config/RELEASE file and
|
||||
add <tt>LIBOBJS</tt> definitions to the src Makefile.</p>
|
||||
|
||||
<p>For example add</p>
|
||||
|
||||
<pre> PID=<full path to modules directory>/pid
|
||||
</pre>
|
||||
|
||||
<p>to config/RELEASE and add <br>
|
||||
|
||||
<pre> LIBOBJS += $(PID_BIN)/pidRecord.o
|
||||
</pre>
|
||||
to your application src/Makefile.
|
||||
|
||||
<p>You should consider changing any existing old steppermotor records to the
|
||||
new EPICS motor record module supported by Beamline Controls and Data
|
||||
Acquisition at APS.</p>
|
||||
|
||||
<h3>RecDynLink.o and devPtSoft changes</h3>
|
||||
|
||||
<p>recDynLink.o and devPtSoft.o are no longer in EPICS base and now exist as
|
||||
separate EPICS modules.You must now add the appropriate module full path
|
||||
definitions to your application config/RELEASE file, and change
|
||||
<tt>LIBOBJS</tt> location definition <tt>$(EPICS_BASE_BIN)</tt> to the module
|
||||
definition bin directory in your application src directory files. See
|
||||
"Hardware support changes" below for instructions.</p>
|
||||
|
||||
<h3>Hardware support changes</h3>
|
||||
|
||||
<p>All hardware support (dev, drv and dbd files) except soft support has been
|
||||
unbundled from base R3.14. This support includes the files symb.dbd,
|
||||
drvHp1404a.o, drvEpvxiMsg.o, and drvEpvxi.o. If these are not used by your
|
||||
application, comment out references to them in base.dbd.</p>
|
||||
|
||||
<p>Hardware support now exists as separate EPICS modules. The hardware
|
||||
support for your site should be downloaded and built with base R3.14 by your
|
||||
EPICS administrator. You must now add the appropriate module full path
|
||||
definitions to your application config/RELEASE file, and change
|
||||
<tt>LIBOBJS</tt> location from <tt>$(EPICS_BASE_BIN) </tt>to the module bin
|
||||
directory in your application src directory files.</p>
|
||||
|
||||
<p>For example, remove</p>
|
||||
|
||||
<pre> LIBOBJS+=$(EPICS_BASE_BIN)/symb
|
||||
</pre>
|
||||
|
||||
<p>from baseLIBOBJS and add</p>
|
||||
|
||||
<pre> LIBOBJS+=$(SYMB_BIN)/symb
|
||||
</pre>
|
||||
|
||||
<p>to your application src/Makefile, <br>
|
||||
and add the line</p>
|
||||
|
||||
<pre> SYMB=<full path definition for the built module SYMB>
|
||||
</pre>
|
||||
|
||||
<p>into your application config/RELEASE file .</p>
|
||||
|
||||
<h3>dbLoadtemplate tool changes</h3>
|
||||
|
||||
<p>The host tool dbLoadTemplate has been replace by a new EPICS extension,
|
||||
msi, which should be downloaded and built with base R3.14 by your EPICS
|
||||
administrator. dbLoadTemplate is still supported on iocs. If, in your
|
||||
application, db files are created from template and substitution files you
|
||||
should add the definition</p>
|
||||
|
||||
<p><tt>MSI=<full path name to msi executable></tt></p>
|
||||
|
||||
<p>to your application config/RELEASE file.</p>
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,45 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
||||
"http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>Converting an EPICS R3.14.6 application to R3.14.7</h2>
|
||||
</center>
|
||||
|
||||
<p>This document describes how to convert a R3.14.6 application so that it
|
||||
builds with release R3.14.7.</p>
|
||||
|
||||
|
||||
<h3>State Notation Compiler flags</h3>
|
||||
|
||||
<blockquote>
|
||||
To make the run-time code reentrant, thus allowing more than one
|
||||
instance of the state program to run on an IOC add the line
|
||||
<pre><name>_SNCFLAGS += +r"</pre> to the Makefile, replacing <name> with the
|
||||
state notation language code file name.
|
||||
</blockquote>
|
||||
|
||||
<h3>epicsExit</h3>
|
||||
<blockquote>
|
||||
Code that calls exit or atexit should change these calls to epicsExit
|
||||
and epicsAtExit. epicsAtExit was created because of problems on
|
||||
vxWorks and windows with the implementation of atexit,
|
||||
i.e. neither of these systems implements exit and atexit according to the POSIX standard.
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
Add the following lines
|
||||
<blockquote>
|
||||
<pre>
|
||||
#include "epicsExit.h"
|
||||
epicsExit(0);
|
||||
</pre>
|
||||
</blockquote>
|
||||
</blockquote>
|
||||
|
||||
@@ -1,23 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
||||
"http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="jba">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h2>Converting an EPICS R3.14.7 application to R3.14.8</h2>
|
||||
</center>
|
||||
|
||||
<p>This document describes how to convert a R3.14.7 application
|
||||
so that it builds and runs properly with release R3.14.8.</p>
|
||||
|
||||
<h3>No changes required.</h3>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
~
|
||||
@@ -4,16 +4,15 @@
|
||||
<html xmlns="http://www.w3.org/1999/xhtml">
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
|
||||
<title>Known Problems in R3.14.11</title>
|
||||
<title>Known Problems in R3.14.12</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1 style="text-align: center">EPICS Base R3.14.11: Known Problems</h1>
|
||||
<h1 style="text-align: center">EPICS Base R3.14.12: Known Problems</h1>
|
||||
|
||||
<ul>
|
||||
|
||||
<li>The epicsMutexTest program sometimes runs an extra test, resulting in
|
||||
a failure report from 'make -s runtests'. This is harmless.</li>
|
||||
<li>None yet.</li>
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -1,511 +1,441 @@
|
||||
README.1st
|
||||
Installation Instructions
|
||||
Installation Instructions
|
||||
|
||||
EPICS base
|
||||
EPICS Base Release 3.14.*
|
||||
|
||||
Release 3.14.*
|
||||
--------------------------------------------------------------------------
|
||||
|
||||
Table of Contents
|
||||
Table of Contents
|
||||
|
||||
* What is EPICS base?
|
||||
* What is new in this release?
|
||||
* Copyright
|
||||
* Supported platforms
|
||||
* Supported compilers
|
||||
* Software requirements
|
||||
* Host system storage requirements
|
||||
* Documentation
|
||||
* WWW pages
|
||||
* Directory Structure
|
||||
* Build related components
|
||||
* Building EPICS base (Unix and Win32)
|
||||
* Example application and extension
|
||||
* Multiple host platforms
|
||||
* What is EPICS base?
|
||||
* What is new in this release?
|
||||
* Copyright
|
||||
* Supported platforms
|
||||
* Supported compilers
|
||||
* Software requirements
|
||||
* Host system storage requirements
|
||||
* Documentation
|
||||
* WWW pages
|
||||
* Directory Structure
|
||||
* Build related components
|
||||
* Building EPICS base (Unix and Win32)
|
||||
* Example application and extension
|
||||
* 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 which application
|
||||
developers can create a control system. This control system can be used to
|
||||
control accelerators, detectors, telescopes, or other scientific
|
||||
experimental equipment. EPICS base is the set of core software, i.e. the
|
||||
components of EPICS without which EPICS would not 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 EPICS base?
|
||||
|
||||
What is new in this release?
|
||||
The Experimental Physics and Industrial Control Systems (EPICS) is an
|
||||
extensible set of software components and tools with which application
|
||||
developers can create a control system. This control system can be used
|
||||
to control accelerators, detectors, telescopes, or other scientific
|
||||
experimental equipment. EPICS base is the set of core software, i.e. the
|
||||
components of EPICS without which EPICS would not function. EPICS base
|
||||
allows an arbitrary number of target systems, IOCs (input/output
|
||||
controllers), and host systems, OPIs (operator interfaces) of various
|
||||
types.
|
||||
|
||||
Please check the RELEASE_NOTES file in the distribution for description of
|
||||
changes and release migration details.
|
||||
What is new in this release?
|
||||
|
||||
Copyright
|
||||
Please check the RELEASE_NOTES file in the distribution for description
|
||||
of changes and release migration details.
|
||||
|
||||
Please review the COPYRIGHT* files included in the distribution for legal
|
||||
terms of usage.
|
||||
Copyright
|
||||
|
||||
Supported platforms
|
||||
Please review the LICENSE file included in the distribution for legal
|
||||
terms of usage.
|
||||
|
||||
Currently this version of EPICS base has been built on the 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.
|
||||
Supported platforms
|
||||
|
||||
Host platforms (operating system - architecture [- alternate toolset])
|
||||
The list of platforms supported by this version of EPICS base is given
|
||||
in the configure/CONFIG_SITE file. If you are trying to build EPICS Base
|
||||
on an unlisted host or for a different target machine you must have 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.
|
||||
|
||||
cygwin-x86 (unix style API, uses cygwin1.dll compatability library)
|
||||
darwin-ppc
|
||||
darwin-x86
|
||||
darwin-ppcx86
|
||||
freebsd-x86
|
||||
freebsd-x86_64
|
||||
linux-ppc
|
||||
linux-x86
|
||||
linux-x86_64
|
||||
linux-x86-borland
|
||||
solaris-sparc
|
||||
solaris-sparc-gnu
|
||||
solaris-sparc64
|
||||
solaris-sparc64-gnu
|
||||
solaris-x86
|
||||
solaris-x86-gnu
|
||||
win32-x86
|
||||
win32-x86-mingw (WIN32 API, uses MS dlls)
|
||||
win32-x86-cygwin (WIN32 API, uses MS dlls)
|
||||
Supported compilers
|
||||
|
||||
Cross compile target platforms (operating system - architecture)
|
||||
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++ compilers.
|
||||
The GNU cross-compilers work for all cross-compiled targets. You may
|
||||
need the C and C++ compilers to be in your search path to do EPICS
|
||||
builds; check the definitions of CC and CCC in
|
||||
base/configure/os/CONFIG.<host>.<host> if you have problems.
|
||||
|
||||
linux-386
|
||||
linux-486
|
||||
linux-586
|
||||
linux-686
|
||||
linux-arm
|
||||
linux-arm_eb
|
||||
linux-arm_el
|
||||
linux-athlon
|
||||
linux-cris
|
||||
linux-cris_v10
|
||||
linux-cris_v32
|
||||
linux-xscale_be
|
||||
vxWorks-486
|
||||
vxWorks-68040
|
||||
vxWorks-68040lc
|
||||
vxWorks-68060
|
||||
vxWorks-pentium
|
||||
vxWorks-ppc603
|
||||
vxWorks-ppc603_long
|
||||
vxWorks-ppc604
|
||||
vxWorks-ppc604_long
|
||||
vxWorks-ppc604_altivec
|
||||
vxWorks-mpc8540
|
||||
RTEMS-at91rm9200ek
|
||||
RTEMS-beatnik
|
||||
RTEMS-gen68360
|
||||
RTEMS-mcp750
|
||||
RTEMS-mvme167
|
||||
RTEMS-mvme2100
|
||||
RTEMS-mvme3100
|
||||
RTEMS-mvme5500
|
||||
RTEMS-pc386
|
||||
RTEMS-psim
|
||||
RTEMS-uC5282
|
||||
Software requirements
|
||||
|
||||
Supported compilers
|
||||
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.
|
||||
|
||||
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++ compilers. The GNU
|
||||
cross-compilers have been used for all 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>.
|
||||
Perl
|
||||
You must have Perl version 5.8.1 or later installed. The EPICS
|
||||
configuration files do not specify the perl full pathname, so the perl
|
||||
executable must be found through your normal search path.
|
||||
|
||||
Software requirements
|
||||
Unzip and tar (Winzip on WIN32 systems)
|
||||
You must have tools available to unzip and untar the EPICS base
|
||||
distribution file.
|
||||
|
||||
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.
|
||||
Target systems
|
||||
EPICS supports IOCs running on embedded platforms such as VxWorks and
|
||||
RTEMS built using a cross-compiler, and also supports soft IOCs running
|
||||
as processes on the host platform.
|
||||
|
||||
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.
|
||||
vxWorks
|
||||
You must have vxWorks installed if any of your target systems are
|
||||
vxWorks systems. This provides the cross-compiler and header files
|
||||
needed to build for these target systems. The absolute path to and
|
||||
version number of the vxWorks installation is normally specified in the
|
||||
base/configure/os/CONFIG_SITE.Common.vxWorksCommon file. Consult the
|
||||
EPICS web pages about [1]vxWorks 5.x and [2]vxWorks 6.x and the
|
||||
vxWorks documentation for information about configuring your vxWorks
|
||||
operating system for use with EPICS.
|
||||
|
||||
Perl
|
||||
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.
|
||||
RTEMS
|
||||
For RTEMS targets, you need RTEMS core and toolset version 4.9.2 or
|
||||
later.
|
||||
|
||||
Unzip and tar (Winzip on WIN32 systems)
|
||||
You must have tools available to unzip and untar the EPICS base distribution
|
||||
file.
|
||||
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.
|
||||
GNU readline (or Tecla library) must be installed on your target system
|
||||
when COMMANDLINE_LIBRARY is set to READLINE (or TECLA) for that target.
|
||||
EPICS (EPICS shell) is the default specified in CONFIG_COMMON. A
|
||||
READLINE override is defined for linux-x86 in the EPICS distribution.
|
||||
Comment out COMMANDLINE_LIBRARY=READLINE in
|
||||
configure/os/CONFIG_SITE.Common.linux-x86 if readline is not installed
|
||||
on linux-x86. Command-line editing and history will then be those
|
||||
supplied by the os. On vxWorks the ledLib command-line input library is
|
||||
used instead.
|
||||
|
||||
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.
|
||||
Host system storage requirements
|
||||
|
||||
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 needed to
|
||||
build for these target systems. The full path location to 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.
|
||||
The GNU zipped tar file is approximately 1.5 MB in size. The unzipped
|
||||
untarred distribution source tree is approximately 9.0 MB. The build
|
||||
created files for each host take approximately 37 MB and the build
|
||||
created files for each cross target take approximately 15 MB.
|
||||
|
||||
RTEMS
|
||||
For RTEMS targets, you need RTEMS core and toolset version 4.9.2 or later.
|
||||
Documentation
|
||||
|
||||
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. GNU readline
|
||||
(or Tecla library) must be installed on your target system when
|
||||
COMMANDLINE_LIBRARY is set to READLINE (or TECLA) for that target. EPICS
|
||||
(EPICS shell) is the default specified in CONFIG_COMMON. A READLINE override
|
||||
is defined for linux-x86 in the EPICS distribution. Comment out
|
||||
COMMANDLINE_LIBRARY=READLINE in configure/os/CONFIG_SITE.Common.linux-x86 if
|
||||
readline is not installed on linux-x86. Command-line editing and history
|
||||
will then be those supplied by the os. On vxWorks the ledLib command-line
|
||||
input libraries are used.
|
||||
EPICS documentation is available through the [3]EPICS website at
|
||||
Argonne.
|
||||
|
||||
Host system storage requirements
|
||||
Release specific documenataion can also be found in the
|
||||
base/documentation directory of the distribution.
|
||||
|
||||
The GNU zipped tar file is approximately 1.5 MB in size. The unzipped
|
||||
untarred distribution source tree is approximately 7.4 MB. The build created
|
||||
files for each host take approximately 37 MB and the build created files for
|
||||
each cross target take approximately 15 MB.
|
||||
|
||||
Documentation
|
||||
|
||||
EPICS documentation is available on the WWW via the EPICS home page at APS:
|
||||
URL http://www.aps.anl.gov/epics by selecting IOC software/ Base R3.14/
|
||||
<release number>.
|
||||
|
||||
Release specific documentation can be found in the base/documentation
|
||||
directory of the distribution.
|
||||
|
||||
WWW pages
|
||||
|
||||
EPICS home page at APS
|
||||
|
||||
http://www.aps.anl.gov/epics
|
||||
|
||||
Other WWW sites
|
||||
|
||||
Additional information on EPICS can be found at the various other WWW
|
||||
links on the EPICS home page at APS.
|
||||
|
||||
Mailing List
|
||||
|
||||
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
|
||||
Directory Structure
|
||||
|
||||
Distribution directory structure:
|
||||
|
||||
base Root directory of the base distribution
|
||||
base/config R3.13 compatibility build configuration files
|
||||
base/config/tools Perl and shell scripts used in the R3.13 build
|
||||
base/configure Operating system independent build config files
|
||||
base/configure/os Operating system dependent build config files
|
||||
base/documentation Distributation documentation
|
||||
base/src All epics base source code in subdirectories
|
||||
base/src/RTEMS Code to configure RTEMS for EPICS
|
||||
base/src/as Access security
|
||||
base/src/bpt Break point table
|
||||
base/src/ca Channel access
|
||||
base/src/cap5 Channel Access client interface for Perl 5
|
||||
base/src/cas Channel access server library and examples
|
||||
base/src/catools Channel access tools caget, cainfo, camonitor, caput
|
||||
base/src/db Database access
|
||||
base/src/db/test Database access tests
|
||||
base/src/dbStatic Static database access
|
||||
base/src/dbtools Database dbLoadTemplate tools
|
||||
base/src/dev Device support (camacDev, softDev, and testDev)
|
||||
base/src/excas Example channel access server
|
||||
base/src/gdd General data descriptor
|
||||
base/src/libCom General purpose library code in subdirectories
|
||||
base/src/libCom/bucketLib Hash bucket
|
||||
base/src/libCom/calc Algebraic expression interpreter
|
||||
base/src/libCom/cppStd Support for C++ standard template library
|
||||
base/src/libCom/cvtFast Fast number to string conversion
|
||||
base/src/libCom/cxxTemplates C++ templates and templates tests
|
||||
base/src/libCom/dbmf Memory management for frequent alloc/free
|
||||
base/src/libCom/ellLib EPICS double linked list
|
||||
base/src/libCom/env Default EPICS environment settings
|
||||
base/src/libCom/error Error handling definitions and routines
|
||||
base/src/libCom/fdmgr File descriptor manager
|
||||
base/src/libCom/freeList Memory management using free lists
|
||||
base/src/libCom/gpHash General purpose hash table
|
||||
base/src/libCom/iocsh ioc shell call registered functions
|
||||
base/src/libCom/logClient Logging client
|
||||
base/src/libCom/macLib Macro substitution handler
|
||||
base/src/libCom/misc Miscellaneous utilities
|
||||
base/src/libCom/osi Operating system independent code
|
||||
base/src/libCom/osi/os Operating system dependant code in subdirectories
|
||||
base/src/libCom/ring Methods for creating and using ring buffers
|
||||
base/src/libCom/taskwd Task watchdog
|
||||
base/src/libCom/test Test tools (timer, semBinary, semMutex,fdmgr, ...)
|
||||
base/src/libCom/timer Timer
|
||||
base/src/libCom/tsDefs R3.13 time stamp definitions and routines
|
||||
base/src/makeBaseApp Perl tool+templates to create ioc app dvl tree
|
||||
base/src/makeBaseExt Perl tool+templates to create extension dvl tree
|
||||
base/src/misc Miscellaneous (coreRelease, iocInit, asSub*)
|
||||
base/src/rec Record support
|
||||
base/src/registry EPICS support function registry
|
||||
base/src/rsrv Channel access ioc resource server library
|
||||
base/src/softIoc Example softIoc
|
||||
base/src/tools Perl scripts used during the builds
|
||||
base/src/toolsComm Code for the build tools antelope and e_flex
|
||||
base/src/util Utilities (ca_test, iocLogServer, startCArepeater)
|
||||
base/src/vxWorks R3.13 compatibility code specific to vxWorks
|
||||
base/startup Scripts for setting up path and environment
|
||||
base Root directory of the base distribution
|
||||
base/config R3.13 compatibility build configuration files
|
||||
base/config/tools Perl and shell scripts used in the R3.13 build
|
||||
base/configure Operating system independent build config files
|
||||
base/configure/os Operating system dependent build config files
|
||||
base/configure/tools Perl and shell scripts used in the build
|
||||
base/documentation Distributation documentation
|
||||
base/src All epics base source code in subdirectories
|
||||
base/src/RTEMS Code to configure RTEMS for EPICS
|
||||
base/src/as Access security
|
||||
base/src/bpt Break point table
|
||||
base/src/ca Channel access
|
||||
base/src/cap5 Channel Access client interface for Perl 5
|
||||
base/src/cas Channel access server library and examples
|
||||
base/src/catools Channel access tools caget, cainfo, camonitor, caput
|
||||
base/src/db Database access
|
||||
base/src/db/test Database access tests
|
||||
base/src/dbStatic Static database access
|
||||
base/src/dbtools Database dbLoadTemplate tools
|
||||
base/src/dev Device support (camacDev, softDev, and testDev)
|
||||
base/src/excas Example channel access server
|
||||
base/src/gdd General data descriptor
|
||||
base/src/libCom General purpose library code in subdirectories
|
||||
base/src/libCom/bucketLib Hash bucket
|
||||
base/src/libCom/calc Algebraic expression interpreter
|
||||
base/src/libCom/cppStd Support for C++ standard template library
|
||||
base/src/libCom/cvtFast Fast number to string conversion
|
||||
base/src/libCom/cxxTemplates C++ templates and templates tests
|
||||
base/src/libCom/dbmf Memory management for frequent alloc/free
|
||||
base/src/libCom/ellLib EPICS double linked list
|
||||
base/src/libCom/env Default EPICS environment settings
|
||||
base/src/libCom/error Error handling definitions and routines
|
||||
base/src/libCom/fdmgr File descriptor manager
|
||||
base/src/libCom/freeList Memory management using free lists
|
||||
base/src/libCom/gpHash General purpose hash table
|
||||
base/src/libCom/logClient Logging client
|
||||
base/src/libCom/macLib Macro substitution handler
|
||||
base/src/libCom/misc Miscellaneous utilities
|
||||
base/src/libCom/osi Operating system independent API
|
||||
base/src/libCom/osi/os Operating system dependant code in subdirectories
|
||||
base/src/libCom/ring Methods for creating and using ring buffers
|
||||
base/src/libCom/taskwd Task watchdog
|
||||
base/src/libCom/test Test tools (timer, semBinary, semMutex,fdmgr, ...)
|
||||
base/src/libCom/timer Timer
|
||||
base/src/libCom/tsDefs R3.13 time stamp definitions and routines
|
||||
base/src/makeBaseApp Perl tool+templates to create ioc app dvl tree
|
||||
base/src/makeBaseExt Perl tool+templates to create extension dvl tree
|
||||
base/src/misc Miscellaneous (coreRelease, iocInit, asSub*)
|
||||
base/src/rec Record support
|
||||
base/src/registry EPICS support function registry
|
||||
base/src/rsrv Channel access ioc resource server library
|
||||
base/src/softIoc Example softIoc
|
||||
base/src/tools Perl scripts used during the builds
|
||||
base/src/toolsComm Code for the build tools antelope and e_flex
|
||||
base/src/util Utilities (ca_test, iocLogServer, startCArepeater)
|
||||
base/src/vxWorks R3.13 compatibility code specific to vxWorks
|
||||
base/startup Scripts for setting up path and environment
|
||||
|
||||
Install directories created by the build:
|
||||
|
||||
bin Installed scripts and executables in subdirs
|
||||
cfg Installed build configuration files
|
||||
db Installed data bases
|
||||
dbd Installed data base definitions
|
||||
doc Installed documentation files
|
||||
html Installed html documentation
|
||||
include Installed header files
|
||||
include/os Installed os specific header files in subdirs
|
||||
javalib Installed java class and jar files
|
||||
lib Installed libraries in arch subdirectories
|
||||
lib/perl Installed perl modules
|
||||
templates Installed templates
|
||||
bin Installed scripts and executables in subdirs
|
||||
cfg Installed build configuration files
|
||||
db Installed data bases
|
||||
dbd Installed data base definitions
|
||||
doc Installed documentation files
|
||||
html Installed html documentation
|
||||
include Installed header files
|
||||
include/os Installed os specific header files in subdirs
|
||||
javalib Installed java class and jar files
|
||||
lib Installed libraries in arch subdirectories
|
||||
lib/perl Installed perl modules
|
||||
templates Installed templates
|
||||
|
||||
Build related components
|
||||
Build related components
|
||||
|
||||
base/documentation files
|
||||
base/documentation/README* files
|
||||
|
||||
README.1st Instructions for setup and building epics base
|
||||
README.html html version of README.1st
|
||||
README.WIN32 Microsoft WIN32 specific instructions
|
||||
README.cxxTemplates Information about C++ templates in EPICS base
|
||||
README.niCpu030 NI cpu030 specific instructions
|
||||
README.darwin Installation notes for Mac OS X (Darwin)
|
||||
RELEASE_NOTES.html Notes on release changes
|
||||
KnownProblems.html List of known problems and workarounds
|
||||
Converting*To*.html Release specific conversion instructions
|
||||
Building*With*.html Release specific build instructions
|
||||
README.1st Instructions for setup and building epics base
|
||||
README.html html version of README.1st
|
||||
README.WIN32 Microsoft WIN32 specific instructions
|
||||
README.cxxTemplates Information about C++ templates in EPICS base
|
||||
README.niCpu030 NI cpu030 specific instructions
|
||||
README.darwin Installation notes for Mac OS X (Darwin)
|
||||
RELEASE_NOTES.html Notes on release changes
|
||||
KnownProblems.html List of known problems and workarounds
|
||||
Converting*To*.html Release specific conversion instructions
|
||||
Building*With*.html Release specific build instructions
|
||||
|
||||
base/startup directory - contains scripts to set environment and path
|
||||
|
||||
EpicsHostArch c shell script to set EPICS_HOST_ARCH env variable
|
||||
EpicsHostArch.pl perl script to set EPICS_HOST_ARCH env variable
|
||||
Site.profile bourne shell script to set path and env variables
|
||||
Site.cshrc c shell script to set path and env variables
|
||||
borland.bat WIN32 bat file to set borland path and env variables
|
||||
cygwin.bat WIN32 bat file to set cygwin path and env variables
|
||||
win32.bat WIN32 bat file to set path and env variables
|
||||
EpicsHostArch C shell script to set EPICS_HOST_ARCH env variable
|
||||
EpicsHostArch.pl Perl script to set EPICS_HOST_ARCH env variable
|
||||
Site.profile bourne shell script to set path and env variables
|
||||
Site.cshrc c shell script to set path and env variables
|
||||
borland.bat WIN32 bat file to set borland path and env variables
|
||||
cygwin.bat WIN32 bat file to set cygwin path and env variables
|
||||
win32.bat WIN32 bat file to set path and env variables
|
||||
win32-debug.bat WIN32 debug bat file to set debug path and env variables
|
||||
|
||||
base/configure directory - contains build definitions and rules
|
||||
base/configure directory - contains build definitions and rules
|
||||
|
||||
CONFIG Includes configure files and allows variable overrides
|
||||
CONFIG.CrossCommon Cross build definitions
|
||||
CONFIG.gnuCommon Gnu compiler build definitions for all archs
|
||||
CONFIG_ADDONS Definitions for <osclass> and DEFAULT options
|
||||
CONFIG_BASE EPICS base tool and location definitions
|
||||
CONFIG_BASE_VERSION Definitions for EPICS base version number
|
||||
CONFIG_COMMON Definitions common to all builds
|
||||
CONFIG_ENV Definitions of EPICS environment variables
|
||||
CONFIG_FILE_TYPE Definitions for file types adl,alh,cfg,perlmod,edl
|
||||
CONFIG_SITE Site specific make defintions
|
||||
CONFIG_SITE_ENV Site defaults for EPICS environment variables
|
||||
MAKEFILE Installs CONFIG* RULES* creates CONFIG_APP_INCLUDE
|
||||
RELEASE Location of external products such as Tornado II
|
||||
RULES Includes appropriate rules file
|
||||
RULES.Db Rules for database and database definition files
|
||||
RULES.ioc Rules for application iocBoot/ioc* directory
|
||||
RULES_ARCHS Definitions and rules for building architectures
|
||||
RULES_BUILD Build and install rules and definitions
|
||||
RULES_DIRS Definitions and rules for building subdirectories
|
||||
RULES_EXPAND Devinitions and rules for expanding vars in a file
|
||||
RULES_FILE_TYPE Definitions and rules for user defined file types
|
||||
RULES_JAVA Definitions and rules for java jars and classes
|
||||
RULES_TARGET Definitions and rules for prod and lib named targets
|
||||
RULES_TOP Rules specific to a <top> dir (uninstall and tar)
|
||||
Sample.Makefile Sample makefile with comments
|
||||
|
||||
CONFIG Includes configure files and allows variable overrides
|
||||
CONFIG.CrossCommon Cross build definitions
|
||||
CONFIG.gnuCommon Gnu compiler build definitions for all archs
|
||||
CONFIG_ADDONS Definitions for <osclass> and DEFAULT options
|
||||
CONFIG_BASE EPICS base tool and location definitions
|
||||
CONFIG_BASE_VERSION Definitions for EPICS base version number
|
||||
CONFIG_COMMON Definitions common to all builds
|
||||
CONFIG_ENV Definitions of EPICS environment variables
|
||||
CONFIG_SITE Site specific make defintions
|
||||
CONFIG_SITE_ENV Site defaults for EPICS environment variables
|
||||
MAKEFILE Installs CONFIG* RULES* creates
|
||||
CONFIG_APP_INCLUDE
|
||||
RELEASE Location of external products
|
||||
RULES Includes appropriate rules file
|
||||
RULES.Db Rules for database and database definition files
|
||||
RULES.ioc Rules for application iocBoot/ioc* directory
|
||||
RULES_ARCHS Definitions and rules for building architectures
|
||||
RULES_BUILD Build and install rules and definitions
|
||||
RULES_DIRS Definitions and rules for building subdirectories
|
||||
RULES_JAVA Definitions and rules for java jars and classes
|
||||
RULES_TOP Rules specific to a <top> dir (uninstall and tar)
|
||||
Sample.Makefile Sample makefile with comments
|
||||
|
||||
base/configure/os directory - contains os-arch specific definitions
|
||||
|
||||
CONFIG.<host>.<target> Specific host-target build definitions
|
||||
CONFIG.Common.<target> Specific target definitions for all hosts
|
||||
CONFIG.<host>.Common Specific host definitions for all targets
|
||||
CONFIG.UnixCommon.Common Definitions for Unix hosts and all targets
|
||||
CONFIG.Common.UnixCommon Definitions for Unix targets and all hosts
|
||||
CONFIG.Common.vxWorksCommon Definitions for all vx targets for all hosts
|
||||
CONFIG_COMPAT R3.13 arch compatibility definitions
|
||||
CONFIG_SITE.<host>.<target> Site specific host-target definitions
|
||||
CONFIG_SITE.Common.<target> Site specific target defs for all hosts
|
||||
CONFIG_SITE.<host>.Common Site specific host defs for all targets
|
||||
|
||||
CONFIG.<host>.<target> Specific host-target build definitions
|
||||
CONFIG.Common.<target> Specific target definitions for all hosts
|
||||
CONFIG.<host>.Common Specific host definitions for all targets
|
||||
CONFIG.UnixCommon.Common Definitions for Unix hosts and all targets
|
||||
CONFIG.Common.UnixCommon Definitions for Unix targets and all hosts
|
||||
CONFIG.Common.vxWorksCommon Specific host definitions for all vx targets
|
||||
CONFIG_COMPAT R3.13 arch compatibility definitions
|
||||
CONFIG_SITE.<host>.<target> Site specific host-target definitions
|
||||
CONFIG_SITE.Common.<target> Site specific target defs for all hosts
|
||||
CONFIG_SITE.<host>.Common Site specific host defs for all targets
|
||||
|
||||
base/src/tools directory - contains Perl scripts used for the build
|
||||
|
||||
Makefile Makefile for installing the scripts into cfg dir
|
||||
convertRelease.pl Performs consistancy checks on RELEASE files
|
||||
cvsclean.pl Remove all .#* files in directory tree
|
||||
dos2unix.pl Converts text file from DOS CR/LF to unix ISO
|
||||
expandvars.pl Tool to expand @VAR@ variables while copying a file
|
||||
filterWarnings.pl Filters warning messages during HP builds
|
||||
fullpathName.pl Returns fullpath name of directory arg
|
||||
installEpics.pl Installs built files into install directories
|
||||
makeDbDepends.pl Gets dependencies from .substitution/.template files
|
||||
makeIncludeDbd.pl Creates *Include.dbd file from filename args files
|
||||
makeMakefile.pl Creates a Makefile in O.<arch> dirs
|
||||
makeTestfile.pl Generates a test harness $target.t file
|
||||
mkmf.pl Generates dependencies from include stmnts
|
||||
munch.pl Creates a ctdt.c file for vxWorks targets
|
||||
replaceVAR.pl Changes CapFast VAR(xxx) to $(xxx) notation
|
||||
useManifestTool.pl Use MS VC++ version to set usage of Manifest Tool
|
||||
Makefile Makefile for installing the scripts into cfg dir
|
||||
convertRelease.pl Performs consistancy checks on RELEASE files
|
||||
cvsclean.pl Remove all .#* files in directory tree
|
||||
dos2unix.pl Converts text file from DOS CR/LF to unix ISO
|
||||
expandvars.pl Tool to expand @VAR@ variables while copying a file
|
||||
filterWarnings.pl Filters warning messages during HP builds
|
||||
fullpathName.pl Returns fullpath name of directory arg
|
||||
installEpics.pl Installs built files into install directories
|
||||
makeIncludeDbd.pl Creates *Include.dbd file from filename args files
|
||||
makeMakefile.pl Creates a Makefile in O.<arch> dirs
|
||||
makeTestfile.pl Generates a test harness $target.t file
|
||||
mkmf.pl Generates dependencies from include stmnts
|
||||
munch.pl Creates a ctdt.c file for vxWorks targets
|
||||
replaceVAR.pl Changes CapFast VAR(xxx) to $(xxx) notation
|
||||
useManifestTool.pl Use MS VC++ version to set usage of Manifest Tool
|
||||
|
||||
Building EPICS base (Unix and Win32)
|
||||
Building EPICS base (Unix and Win32)
|
||||
|
||||
Unpack file
|
||||
|
||||
Unzip and untar the distribution file. Use WinZip on Windows systems.
|
||||
Unzip and untar the distribution file. Use WinZip on Windows systems.
|
||||
|
||||
Set environment variables
|
||||
|
||||
Files in the base/startup directory have been provided to help set
|
||||
required path and other 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.
|
||||
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>.
|
||||
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 ln,
|
||||
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 as and ld in your path. On solaris
|
||||
systems you need uname in your path.
|
||||
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 ln, 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 as and ld in your path. On
|
||||
solaris systems you need uname in your path.
|
||||
|
||||
LD_LIBRARY_PATH
|
||||
It is no longer necessary to have LD_LIBRARY_PATH include EPICS
|
||||
directories on a Unix type system. R3.14 shared libraries and
|
||||
executables will contain the full path name to libraries they require.
|
||||
However, if you move the EPICS directories from their build-time
|
||||
location then in order for libraries to be found at runtime
|
||||
LD_LIBRARY_PATH must include the full pathname to
|
||||
$(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) when invoking executables.
|
||||
Building shared libraries is now the default setting for all Unix type
|
||||
hosts. NOTE: You will still need LD_LIBRARY_PATH for R3.13 extension
|
||||
shared libraries even if the R3.13 extensions are built with R3.14 base.
|
||||
LD_LIBRARY_PATH
|
||||
It is no longer necessary to have LD_LIBRARY_PATH include EPICS
|
||||
directories on a Unix type system. R3.14 shared libraries and
|
||||
executables will contain the full path name to libraries they require.
|
||||
However, if you move the EPICS directories from their build-time
|
||||
location then in order for libraries to be found at runtime
|
||||
LD_LIBRARY_PATH must include the full pathname to
|
||||
$(INSTALL_LOCATION)/lib/$(EPICS_HOST_ARCH) when invoking executables.
|
||||
Building shared libraries is now the default setting for all Unix type
|
||||
hosts. NOTE: You will still need LD_LIBRARY_PATH for R3.13 extension
|
||||
shared libraries even if the R3.13 extensions are built with R3.14
|
||||
base.
|
||||
|
||||
Win32 PATH
|
||||
On WIN32 systems, for R3.14.7 and later, it is no longer necessary to
|
||||
add fullpathname to $(INSTALL_LOCATION)/bin/$(EPICS_HOST_ARCH) to your
|
||||
path for finding dlls during EPICS builds. The win32 configure files in
|
||||
base now add this directory to the path definition.
|
||||
Win32 PATH
|
||||
On WIN32 systems, for R3.14.7 and later, it is no longer necessary to
|
||||
add fullpathname to $(INSTALL_LOCATION)/bin/$(EPICS_HOST_ARCH) to your
|
||||
path for finding dlls during EPICS builds. The win32 configure files
|
||||
in base now add this directory to the path definition.
|
||||
|
||||
Do site-specific build configuration
|
||||
|
||||
Site configuration
|
||||
To configure EPICS, you may want to modify the default definitions in
|
||||
the following files:
|
||||
Site configuration
|
||||
To configure EPICS, you may want to modify the default definitions in
|
||||
the following files:
|
||||
|
||||
configure/CONFIG_SITE Build choices. Specify target archs.
|
||||
configure/CONFIG_SITE_ENV Environment variable defaults
|
||||
configure/RELEASE TORNADO2 full path location
|
||||
configure/CONFIG_SITE Build choices. Specify target archs.
|
||||
configure/CONFIG_SITE_ENV Environment variable defaults
|
||||
configure/RELEASE TORNADO2 full path location
|
||||
|
||||
Host configuration
|
||||
To configure each host system, you may override the default definitions
|
||||
by adding a new file in the configure/os directory with override
|
||||
definitions. The new file should have the same name as the distribution
|
||||
file to be overridden except with CONFIG in the name changed to
|
||||
CONFIG_SITE.
|
||||
Host configuration
|
||||
To configure each host system, you may override the default
|
||||
definitions by adding a new file in the configure/os directory with
|
||||
override definitions. The new file should have the same name as the
|
||||
distribution file to be overridden except with CONFIG in the name
|
||||
changed to CONFIG_SITE.
|
||||
|
||||
configure/os/CONFIG.<host>.<host> Host build settings
|
||||
configure/os/CONFIG.<host>.Common Host common build settings
|
||||
configure/os/CONFIG.<host>.<host> Host build settings
|
||||
configure/os/CONFIG.<host>.Common Host common build settings
|
||||
|
||||
Target configuration
|
||||
To configure each target system, you may override the default
|
||||
definitions by adding a new file in the configure/os directory with
|
||||
override definitions. The new file should have the same name as the
|
||||
distribution file to be overridden except with CONFIG in the name
|
||||
replaced by CONFIG_SITE. This step is necessary even if the host system
|
||||
is the only target system.
|
||||
Target configuration
|
||||
To configure each target system, you may override the default
|
||||
definitions by adding a new file in the configure/os directory with
|
||||
override definitions. The new file should have the same name as the
|
||||
distribution file to be overridden except with CONFIG in the name
|
||||
replaced by CONFIG_SITE. This step is necessary even if the host
|
||||
system is the only target system.
|
||||
|
||||
configure/os/CONFIG.Common.<target> Target common settings
|
||||
configure/os/CONFIG.<host>.<target> Host-target settings
|
||||
configure/os/CONFIG.Common.<target> Target common settings
|
||||
configure/os/CONFIG.<host>.<target> Host-target 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 definitions you made in
|
||||
base/configure and base/configure/os files.
|
||||
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 definitions you made in
|
||||
base/configure and base/configure/os files.
|
||||
|
||||
Build EPICS base
|
||||
|
||||
After configuring the build you should be able to build EPICS base by
|
||||
issuing the following commands in the distribution's root directory
|
||||
(base)
|
||||
After configuring the build you should be able to build EPICS base by
|
||||
issuing the following commands in the distribution's root directory
|
||||
(base):
|
||||
|
||||
gnumake clean uninstall
|
||||
gnumake
|
||||
gnumake clean uninstall
|
||||
gnumake
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
It is recommended that you do a "gnumake clean uninstall" at the root
|
||||
directory of an EPICS directory structure before each complete rebuild
|
||||
to ensure that all components will be rebuilt.
|
||||
It is recommended that you do a "gnumake clean uninstall" at the root
|
||||
directory of an EPICS directory structure before each complete rebuild
|
||||
to ensure that all components will be rebuilt.
|
||||
|
||||
Example application and extension
|
||||
Example application and extension
|
||||
|
||||
A perl tool, makeBaseApp.pl is included in the distribution file. This
|
||||
script will create a sample application that can be built and then executed
|
||||
to try out this release of base.
|
||||
A perl tool, makeBaseApp.pl is included in the distribution file. This
|
||||
script will create a sample application that can be built and then
|
||||
executed to try out this release of base.
|
||||
|
||||
Instructions for building and executing the 3.14 example application can be
|
||||
found in the section "Example Application" of Chapter 2, "Getting Started",
|
||||
in the "IOC Application Developer's Guide" for this release. The "Example
|
||||
IOC 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 as a process on the host system.
|
||||
By running the example application as a host-based IOC, you will be able
|
||||
to quickly implement a complete EPICS system and be able to run channel
|
||||
access clients on the host system.
|
||||
Instructions for building and executing the 3.14 example application can
|
||||
be found in the section "Example Application" of Chapter 2, "Getting
|
||||
Started", in the "IOC Application Developer's Guide" for this release.
|
||||
The "Example IOC 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 as a
|
||||
process on the host system. By running the example application as a
|
||||
host-based IOC, you will be able to quickly implement a complete EPICS
|
||||
system and be able to run channel access clients on the host system.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
Multiple host platforms
|
||||
Multiple host platforms
|
||||
|
||||
You can build using a single EPICS directory structure on multiple host
|
||||
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/<arch> directories. Libraries are installed into
|
||||
$(INSTALL_LOCATION)/lib/<arch>. 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.<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/c++ cross compiler and target header files and the base/configure/os
|
||||
directory must have the appropriate configure files.
|
||||
You can build using a single EPICS directory structure on multiple host
|
||||
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/<arch> directories. Libraries are
|
||||
installed into $(INSTALL_LOCATION)/lib/<arch>. 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.<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/C++ cross compiler and target header files and the
|
||||
base/configure/os directory must have the appropriate configure files.
|
||||
|
||||
References
|
||||
|
||||
1. http://www.aps.anl.gov/epics/base/tornado.php
|
||||
2. http://www.aps.anl.gov/epics/base/vxWorks6.php
|
||||
3. http://www.aps.anl.gov/epics/
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
WARNING: THIS FILE IS OLD
|
||||
=========================
|
||||
|
||||
Some of the information in this file is likely to be out of date. It has not been
|
||||
updated since 2005, so things like the minimum required versions are now wrong.
|
||||
|
||||
|
||||
Compiling EPICS and Building IOC Applications on MS Windows
|
||||
-----------------------------------------------------------
|
||||
|
||||
@@ -1,10 +1,12 @@
|
||||
<!DOCTYPE HTML>
|
||||
<HTML>
|
||||
README.html
|
||||
<HEAD>
|
||||
<TITLE>README - EPICS Base Installation Instructions</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<CENTER>
|
||||
<H1>Installation Instructions</H1>
|
||||
<H2>EPICS base Release 3.14.*</H2><BR>
|
||||
<H2>EPICS Base Release 3.14.*</H2><BR>
|
||||
</CENTER>
|
||||
<HR>
|
||||
<H3> Table of Contents</H3>
|
||||
@@ -42,129 +44,65 @@ README.html
|
||||
description of changes and release migration details.</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_3"> Copyright</A></H3>
|
||||
<BLOCKQUOTE>Please review the COPYRIGHT* files included in the
|
||||
<BLOCKQUOTE>Please review the LICENSE file included in the
|
||||
distribution for legal terms of usage.</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_4"> Supported platforms</A></H3>
|
||||
<BLOCKQUOTE>Currently this version of EPICS base has been built on the
|
||||
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
|
||||
|
||||
<BLOCKQUOTE>The list of platforms supported by this version of EPICS base
|
||||
is given in the configure/CONFIG_SITE file. If you are trying to build
|
||||
EPICS Base on an unlisted host or for a different target machine you
|
||||
must have 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.</BLOCKQUOTE><BLOCKQUOTE>
|
||||
|
||||
<H4>Host platforms (operating system - architecture [- alternate
|
||||
toolset])</H4>
|
||||
<BLOCKQUOTE>
|
||||
<PRE>cygwin-x86 (unix style API, uses cygwin1.dll compatability library)
|
||||
darwin-ppc
|
||||
darwin-x86
|
||||
darwin-ppcx86
|
||||
freebsd-x86
|
||||
freebsd-x86_64
|
||||
linux-ppc
|
||||
linux-x86
|
||||
linux-x86_64
|
||||
linux-x86-borland
|
||||
solaris-sparc
|
||||
solaris-sparc-gnu
|
||||
solaris-sparc64
|
||||
solaris-sparc64-gnu
|
||||
solaris-x86
|
||||
solaris-x86-gnu
|
||||
win32-x86
|
||||
win32-x86-mingw (WIN32 API, uses MS dlls)
|
||||
win32-x86-cygwin (WIN32 API, uses MS dlls)
|
||||
</PRE>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H4> Cross compile target platforms (operating system - architecture)</H4>
|
||||
<BLOCKQUOTE>
|
||||
<PRE>linux-386
|
||||
linux-486
|
||||
linux-586
|
||||
linux-686
|
||||
linux-arm
|
||||
linux-arm_eb
|
||||
linux-arm_el
|
||||
linux-athlon
|
||||
linux-cris
|
||||
linux-cris_v10
|
||||
linux-cris_v32
|
||||
linux-xscale_be
|
||||
vxWorks-486
|
||||
vxWorks-68040
|
||||
vxWorks-68040lc
|
||||
vxWorks-68060
|
||||
vxWorks-pentium
|
||||
vxWorks-ppc603
|
||||
vxWorks-ppc603_long
|
||||
vxWorks-ppc604
|
||||
vxWorks-ppc604_long
|
||||
vxWorks-ppc604_altivec
|
||||
vxWorks-mpc8540
|
||||
RTEMS-at91rm9200ek
|
||||
RTEMS-beatnik
|
||||
RTEMS-gen68360
|
||||
RTEMS-mcp750
|
||||
RTEMS-mvme167
|
||||
RTEMS-mvme2100
|
||||
RTEMS-mvme3100
|
||||
RTEMS-mvme5500
|
||||
RTEMS-pc386
|
||||
RTEMS-psim
|
||||
RTEMS-uC5282
|
||||
</PRE>
|
||||
</BLOCKQUOTE>
|
||||
</BLOCKQUOTE>
|
||||
for your new platforms.</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_5"> Supported compilers</A></H3>
|
||||
<BLOCKQUOTE>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++
|
||||
compilers. The GNU cross-compilers have been used for all
|
||||
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>.</BLOCKQUOTE>
|
||||
|
||||
<BLOCKQUOTE>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++ compilers. The GNU
|
||||
cross-compilers work for all cross-compiled targets. You may need the C and C++
|
||||
compilers to be in your search path to do EPICS builds; check the definitions
|
||||
of CC and CCC in base/configure/os/CONFIG.<host>.<host> if you have
|
||||
problems.</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_6"> Software requirements</A></H3>
|
||||
|
||||
<BLOCKQUOTE><B>GNU make</B>
|
||||
<BR> You must use GNU make, gnumake, for any EPICS builds. Set your path
|
||||
<BLOCKQUOTE><B>GNU make</B><BR>
|
||||
You must use GNU make, gnumake, for any EPICS builds. Set your path
|
||||
so that a gnumake version 3.81 or later is available.
|
||||
|
||||
<P><B>gcc</B>
|
||||
<BR> 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.</P>
|
||||
<P><B>Perl</B><BR>
|
||||
You must have Perl version 5.8.1 or later installed. The EPICS configuration
|
||||
files do not specify the perl full pathname, so the perl executable must
|
||||
be found through your normal search path.</P>
|
||||
|
||||
<P><B>Perl</B>
|
||||
<BR> 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.</P>
|
||||
|
||||
<P><B>Unzip and tar (Winzip on WIN32 systems)</B>
|
||||
<BR> You must have tools available to unzip and untar the EPICS base
|
||||
<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>
|
||||
|
||||
<P><B>Target systems</B>
|
||||
<BR> EPICS supports IOCs running on embedded platforms such as VxWorks
|
||||
and RTEMS via cross-compilers. EPICS also supports ?soft? IOCs running
|
||||
<P><B>Target systems</B><BR>
|
||||
EPICS supports IOCs running on embedded platforms such as VxWorks
|
||||
and RTEMS built using a cross-compiler, and also supports soft IOCs running
|
||||
as processes on the host platform.</P>
|
||||
|
||||
<P><B>Tornado 2</B>
|
||||
<BR> You must have Tornado 2 installed if any of your target systems are
|
||||
vxWorks systems. Tornado 2 provides the cross-compiler and header files
|
||||
needed to build for these target systems. The full path location to
|
||||
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.</P>
|
||||
<P><B>vxWorks</B><BR>
|
||||
You must have vxWorks installed if any of your target systems are
|
||||
vxWorks systems. This provides the cross-compiler and header files
|
||||
needed to build for these target systems. The absolute path to and version
|
||||
number of the vxWorks installation is normally specified in the
|
||||
base/configure/os/CONFIG_SITE.Common.vxWorksCommon file. Consult the EPICS web
|
||||
pages about <a href="http://www.aps.anl.gov/epics/base/tornado.php">vxWorks
|
||||
5.x</a> and <a href="http://www.aps.anl.gov/epics/base/vxWorks6.php">vxWorks
|
||||
6.x</a> and the vxWorks documentation for information about configuring your
|
||||
vxWorks operating system for use with EPICS.</P>
|
||||
|
||||
<P><B>RTEMS</B>
|
||||
<BR> For RTEMS targets, you need RTEMS core and toolset version 4.9.2 or later.</P>
|
||||
<P><B>GNU readline or Tecla library</B>
|
||||
<BR> GNU readline and Tecla librararies can be used by the IOC shell to
|
||||
<P><B>RTEMS</B><BR>
|
||||
For RTEMS targets, you need RTEMS core and toolset version 4.9.2 or later.</P>
|
||||
|
||||
<P><B>GNU readline or Tecla library</B><BR>
|
||||
GNU readline and Tecla librararies can be used by the IOC shell to
|
||||
provide command line editing and command line history recall and edit.
|
||||
GNU readline (or Tecla library) must be installed on your target system
|
||||
when COMMANDLINE_LIBRARY is set to READLINE (or TECLA) for that target.
|
||||
@@ -173,287 +111,207 @@ RTEMS-uC5282
|
||||
Comment out COMMANDLINE_LIBRARY=READLINE in
|
||||
configure/os/CONFIG_SITE.Common.linux-x86 if readline is not installed
|
||||
on linux-x86. Command-line editing and history will then be those
|
||||
supplied by the os. On vxWorks the ledLib command-line input libraries
|
||||
are used.</P>
|
||||
supplied by the os. On vxWorks the ledLib command-line input library is
|
||||
used instead.</P>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_7"> Host system storage requirements</A></H3>
|
||||
<BLOCKQUOTE>The GNU zipped tar file is approximately 1.5 MB in size. The
|
||||
unzipped untarred distribution source tree is approximately 7.4 MB. The
|
||||
unzipped untarred distribution source tree is approximately 9.0 MB. The
|
||||
build created files for each host take approximately 37 MB and the
|
||||
build created files for each cross target take approximately 15 MB.</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_8"> Documentation</A></H3>
|
||||
<BLOCKQUOTE>EPICS documentation is available on the WWW via the EPICS
|
||||
home page at APS: URL<A href="http://www.aps.anl.gov/epics">
|
||||
http://www.aps.anl.gov/epics</A> by selection IOC software/ Base
|
||||
R3.14/ <release number>.
|
||||
</BLOCKQUOTE>
|
||||
<BLOCKQUOTE>Release specific documenataion can be found in the base/documentation
|
||||
directory of the distribution.
|
||||
</BLOCKQUOTE>
|
||||
<H3><A NAME="0_0_9"> WWW pages</A></H3>
|
||||
<BLOCKQUOTE>
|
||||
<H4> EPICS home page at APS</H4>
|
||||
<BLOCKQUOTE><A href="http://www.aps.anl.gov/epics">
|
||||
http://www.aps.anl.gov/epics</A></BLOCKQUOTE>
|
||||
<H4> Other WWW sites</H4>
|
||||
<BLOCKQUOTE>Additional information on EPICS can be found at the various
|
||||
other WWW links on the EPICS home page at APS.</BLOCKQUOTE>
|
||||
<H4> Mailing List</H4>
|
||||
<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>
|
||||
<BLOCKQUOTE>EPICS documentation is available through the
|
||||
<a href="http://www.aps.anl.gov/epics/">EPICS website</a> at Argonne.
|
||||
<P>Release specific documenataion can also be found in the base/documentation
|
||||
directory of the distribution.</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_10"> Directory Structure</A></H3>
|
||||
<BLOCKQUOTE><H4>Distribution directory structure:</H4>
|
||||
<BLOCKQUOTE><TT>
|
||||
base Root directory of the base distribution</TT>
|
||||
<BR> <TT>base/config R3.13 compatibility build
|
||||
configuration files</TT>
|
||||
<BR> <TT>base/config/tools Perl and shell scripts used
|
||||
in the R3.13 build</TT>
|
||||
<BR> <TT>base/configure Operating system independent
|
||||
build config files</TT>
|
||||
<BR> <TT>base/configure/os Operating system dependent
|
||||
build config files</TT>
|
||||
<BR> <TT>base/configure/tools Perl and shell scripts used
|
||||
in the build</TT>
|
||||
<BR> <TT>base/documentation Distributation documentation</TT>
|
||||
<BR> <TT>base/src All epics base source code in
|
||||
subdirectories</TT>
|
||||
<BR> <TT>base/src/RTEMS Code to configure RTEMS for
|
||||
EPICS</TT>
|
||||
<BR> <TT>base/src/as Access security</TT>
|
||||
<BR> <TT>base/src/bpt Break point table</TT>
|
||||
<BR> <TT>base/src/ca Channel access</TT>
|
||||
<BR> <TT>base/src/cap5 Channel Access client
|
||||
interface for Perl 5</TT>
|
||||
<BR> <TT>base/src/cas Channel access server library
|
||||
and examples</TT>
|
||||
<BR> <TT>base/src/catools Channel access tools caget,
|
||||
cainfo, camonitor, caput</TT>
|
||||
<BR> <TT>base/src/db Database access</TT>
|
||||
<BR> <TT>base/src/db/test Database access tests</TT>
|
||||
<BR> <TT>base/src/dbStatic Static database access</TT>
|
||||
<BR> <TT>base/src/dbtools Database dbLoadTemplate tools</TT>
|
||||
<BR> <TT>base/src/dev Device support (camacDev,
|
||||
softDev, and testDev)</TT>
|
||||
<BR> <TT>base/src/excas Example channel access server</TT>
|
||||
<BR> <TT>base/src/gdd General data descriptor</TT>
|
||||
<BR> <TT>base/src/libCom General purpose library code
|
||||
in subdirectories</TT>
|
||||
<BR> <TT>base/src/libCom/bucketLib Hash bucket</TT>
|
||||
<BR> <TT>base/src/libCom/calc Algebraic expression
|
||||
interpreter</TT>
|
||||
<BR> <TT>base/src/libCom/cppStd Support for C++ standard
|
||||
template library</TT>
|
||||
<BR> <TT>base/src/libCom/cvtFast Fast number to string
|
||||
conversion</TT>
|
||||
<BR> <TT>base/src/libCom/cxxTemplates C++ templates and templates
|
||||
tests</TT>
|
||||
<BR> <TT>base/src/libCom/dbmf Memory management for
|
||||
frequent alloc/free</TT>
|
||||
<BR> <TT>base/src/libCom/ellLib EPICS double linked list</TT>
|
||||
<BR> <TT>base/src/libCom/env Default EPICS environment
|
||||
settings</TT>
|
||||
<BR> <TT>base/src/libCom/error Error handling definitions
|
||||
and routines</TT>
|
||||
<BR> <TT>base/src/libCom/fdmgr File descriptor manager</TT>
|
||||
<BR> <TT>base/src/libCom/freeList Memory management using free
|
||||
lists</TT>
|
||||
<BR> <TT>base/src/libCom/gpHash General purpose hash table</TT>
|
||||
<BR> <TT>base/src/libCom/logClient Logging client</TT>
|
||||
<BR> <TT>base/src/libCom/macLib Macro substitution handler</TT>
|
||||
<BR> <TT>base/src/libCom/misc Miscellaneous utilities</TT>
|
||||
<BR> <TT>base/src/libCom/osi Operating system independent
|
||||
code</TT>
|
||||
<BR> <TT>base/src/libCom/osi/os Operating system dependant
|
||||
code in subdirectories</TT>
|
||||
<BR> <TT>base/src/libCom/ring Methods for creating and
|
||||
using ring buffers</TT>
|
||||
<BR> <TT>base/src/libCom/taskwd Task watchdog</TT>
|
||||
<BR> <TT>base/src/libCom/test Test tools (timer, semBinary,
|
||||
semMutex,fdmgr, ...)</TT>
|
||||
<BR> <TT>base/src/libCom/timer Timer</TT>
|
||||
<BR> <TT>base/src/libCom/tsDefs R3.13 time stamp definitions
|
||||
and routines</TT>
|
||||
<BR> <TT>base/src/makeBaseApp Perl tool+templates to create
|
||||
ioc app dvl tree</TT>
|
||||
<BR> <TT>base/src/makeBaseExt Perl tool+templates to create
|
||||
extension dvl tree</TT>
|
||||
<BR> <TT>base/src/misc Miscellaneous (coreRelease,
|
||||
iocInit, asSub*)</TT>
|
||||
<BR> <TT>base/src/rec Record support</TT>
|
||||
<BR> <TT>base/src/registry EPICS support function
|
||||
registry</TT>
|
||||
<BR> <TT>base/src/rsrv Channel access ioc resource
|
||||
server library</TT>
|
||||
<BR> <TT>base/src/softIoc Example softIoc</TT>
|
||||
<BR> <TT>base/src/tools Perl scripts used during the
|
||||
builds</TT>
|
||||
<BR> <TT>base/src/toolsComm Code for the build tools
|
||||
antelope and e_flex</TT>
|
||||
<BR> <TT>base/src/util Utilities (ca_test,
|
||||
iocLogServer, startCArepeater)</TT>
|
||||
<BR> <TT>base/src/vxWorks R3.13 compatibility code
|
||||
specific to vxWorks</TT>
|
||||
<BR> <TT>base/startup Scripts for setting up path
|
||||
and environment</TT>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<PRE>
|
||||
base Root directory of the base distribution
|
||||
base/config R3.13 compatibility build configuration files
|
||||
base/config/tools Perl and shell scripts used in the R3.13 build
|
||||
base/configure Operating system independent build config files
|
||||
base/configure/os Operating system dependent build config files
|
||||
base/configure/tools Perl and shell scripts used in the build
|
||||
base/documentation Distributation documentation
|
||||
base/src All epics base source code in subdirectories
|
||||
base/src/RTEMS Code to configure RTEMS for EPICS
|
||||
base/src/as Access security
|
||||
base/src/bpt Break point table
|
||||
base/src/ca Channel access
|
||||
base/src/cap5 Channel Access client interface for Perl 5
|
||||
base/src/cas Channel access server library and examples
|
||||
base/src/catools Channel access tools caget, cainfo, camonitor, caput
|
||||
base/src/db Database access
|
||||
base/src/db/test Database access tests
|
||||
base/src/dbStatic Static database access
|
||||
base/src/dbtools Database dbLoadTemplate tools
|
||||
base/src/dev Device support (camacDev, softDev, and testDev)
|
||||
base/src/excas Example channel access server
|
||||
base/src/gdd General data descriptor
|
||||
base/src/libCom General purpose library code in subdirectories
|
||||
base/src/libCom/bucketLib Hash bucket
|
||||
base/src/libCom/calc Algebraic expression interpreter
|
||||
base/src/libCom/cppStd Support for C++ standard template library
|
||||
base/src/libCom/cvtFast Fast number to string conversion
|
||||
base/src/libCom/cxxTemplates C++ templates and templates tests
|
||||
base/src/libCom/dbmf Memory management for frequent alloc/free
|
||||
base/src/libCom/ellLib EPICS double linked list
|
||||
base/src/libCom/env Default EPICS environment settings
|
||||
base/src/libCom/error Error handling definitions and routines
|
||||
base/src/libCom/fdmgr File descriptor manager
|
||||
base/src/libCom/freeList Memory management using free lists
|
||||
base/src/libCom/gpHash General purpose hash table
|
||||
base/src/libCom/logClient Logging client
|
||||
base/src/libCom/macLib Macro substitution handler
|
||||
base/src/libCom/misc Miscellaneous utilities
|
||||
base/src/libCom/osi Operating system independent API
|
||||
base/src/libCom/osi/os Operating system dependant code in subdirectories
|
||||
base/src/libCom/ring Methods for creating and using ring buffers
|
||||
base/src/libCom/taskwd Task watchdog
|
||||
base/src/libCom/test Test tools (timer, semBinary, semMutex,fdmgr, ...)
|
||||
base/src/libCom/timer Timer
|
||||
base/src/libCom/tsDefs R3.13 time stamp definitions and routines
|
||||
base/src/makeBaseApp Perl tool+templates to create ioc app dvl tree
|
||||
base/src/makeBaseExt Perl tool+templates to create extension dvl tree
|
||||
base/src/misc Miscellaneous (coreRelease, iocInit, asSub*)
|
||||
base/src/rec Record support
|
||||
base/src/registry EPICS support function registry
|
||||
base/src/rsrv Channel access ioc resource server library
|
||||
base/src/softIoc Example softIoc
|
||||
base/src/tools Perl scripts used during the builds
|
||||
base/src/toolsComm Code for the build tools antelope and e_flex
|
||||
base/src/util Utilities (ca_test, iocLogServer, startCArepeater)
|
||||
base/src/vxWorks R3.13 compatibility code specific to vxWorks
|
||||
base/startup Scripts for setting up path and environment
|
||||
</PRE>
|
||||
|
||||
<H4>Install directories created by the build:</H4>
|
||||
<BLOCKQUOTE>
|
||||
<P><TT>bin Installed scripts and executables in
|
||||
subdirs</TT>
|
||||
<BR> <TT>cfg Installed build configuration
|
||||
files</TT>
|
||||
<BR> <TT>db Installed data bases</TT>
|
||||
<BR> <TT>dbd Installed data base definitions</TT>
|
||||
<BR> <TT>doc Installed documentation files</TT>
|
||||
<BR> <TT>html Installed html documentation</TT>
|
||||
<BR> <TT>include Installed header files</TT>
|
||||
<BR> <TT>include/os Installed os specific header files
|
||||
in subdirs</TT>
|
||||
<BR> <TT>javalib Installed java class and jar files</TT>
|
||||
<BR> <TT>lib Installed libraries in arch
|
||||
subdirectories</TT>
|
||||
<BR> <TT>lib/perl Installed perl modules</TT>
|
||||
<BR> <TT>templates Installed templates</TT></P>
|
||||
</BLOCKQUOTE>
|
||||
<PRE>
|
||||
bin Installed scripts and executables in subdirs
|
||||
cfg Installed build configuration files
|
||||
db Installed data bases
|
||||
dbd Installed data base definitions
|
||||
doc Installed documentation files
|
||||
html Installed html documentation
|
||||
include Installed header files
|
||||
include/os Installed os specific header files in subdirs
|
||||
javalib Installed java class and jar files
|
||||
lib Installed libraries in arch subdirectories
|
||||
lib/perl Installed perl modules
|
||||
templates Installed templates
|
||||
</PRE>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_11"> Build related components</A></H3>
|
||||
<BLOCKQUOTE>
|
||||
<H4> base/documentation/README* files</H4>
|
||||
<BLOCKQUOTE>
|
||||
<TT>README.1st Instructions for setup and building epics
|
||||
base</TT>
|
||||
<BR> <TT>README.html html version of README.1st</TT>
|
||||
<BR> <TT>README.WIN32 Microsoft WIN32 specific instructions</TT>
|
||||
<BR> <TT>README.cxxTemplates Information about C++ templates in EPICS
|
||||
base</TT>
|
||||
<BR> <TT>README.niCpu030 NI cpu030 specific instructions</TT>
|
||||
<BR> <TT>README.darwin Installation notes for Mac OS X (Darwin)</TT>
|
||||
<BR> <TT>RELEASE_NOTES.html Notes on release changes</TT>
|
||||
<BR> <TT>KnownProblems.html List of known problems and workarounds</TT>
|
||||
<BR> <TT>Converting*To*.html Release specific conversion instructions</TT>
|
||||
<BR> <TT>Building*With*.html Release specific build instructions</TT>
|
||||
</BLOCKQUOTE>
|
||||
<H4> base/startup directory - contains scripts to set environment and path</H4>
|
||||
<BLOCKQUOTE>
|
||||
<TT>EpicsHostArch c shell script to set EPICS_HOST_ARCH env
|
||||
variable</TT>
|
||||
<BR> <TT>EpicsHostArch.pl perl script to set EPICS_HOST_ARCH env
|
||||
variable</TT>
|
||||
<BR> <TT>Site.profile bourne shell script to set path and env
|
||||
variables</TT>
|
||||
<BR> <TT>Site.cshrc c shell script to set path and env
|
||||
variables</TT>
|
||||
<BR> <TT>borland.bat WIN32 bat file to set borland path and env
|
||||
variables</TT>
|
||||
<BR> <TT>cygwin.bat WIN32 bat file to set cygwin path and env
|
||||
variables</TT>
|
||||
<BR> <TT>win32.bat WIN32 bat file to set path and env
|
||||
variables</TT>
|
||||
<BR> <TT>win32-debug.bat WIN32 debug bat file to set debug path and
|
||||
env variables</TT>
|
||||
</BLOCKQUOTE>
|
||||
<H4> base/configure directory - contains build definitions and rules</H4>
|
||||
<BLOCKQUOTE>
|
||||
<TT>CONFIG Includes configure files and allows
|
||||
variable overrides</TT>
|
||||
<BR> <TT>CONFIG.CrossCommon Cross build definitions</TT>
|
||||
<BR> <TT>CONFIG.gnuCommon Gnu compiler build definitions for all
|
||||
archs</TT>
|
||||
<BR> <TT>CONFIG_ADDONS Definitions for <osclass> and DEFAULT
|
||||
options</TT>
|
||||
<BR> <TT>CONFIG_BASE EPICS base tool and location definitions</TT>
|
||||
<BR> <TT>CONFIG_BASE_VERSION Definitions for EPICS base version number</TT>
|
||||
<BR> <TT>CONFIG_COMMON Definitions common to all builds</TT>
|
||||
<BR> <TT>CONFIG_ENV Definitions of EPICS environment
|
||||
variables</TT>
|
||||
<BR> <TT>CONFIG_SITE Site specific make defintions</TT>
|
||||
<BR> <TT>CONFIG_SITE_ENV Site defaults for EPICS environment
|
||||
variables</TT>
|
||||
<BR> <TT>MAKEFILE Installs CONFIG* RULES* creates
|
||||
CONFIG_APP_INCLUDE</TT>
|
||||
<BR> <TT>RELEASE Location of external products such as
|
||||
Tornado II</TT>
|
||||
<BR> <TT>RULES Includes appropriate rules file</TT>
|
||||
<BR> <TT>RULES.Db Rules for database and database
|
||||
definition files</TT>
|
||||
<BR> <TT>RULES.ioc Rules for application iocBoot/ioc*
|
||||
directory</TT>
|
||||
<BR> <TT>RULES_ARCHS Definitions and rules for building
|
||||
architectures</TT>
|
||||
<BR> <TT>RULES_BUILD Build and install rules and definitions</TT>
|
||||
<BR> <TT>RULES_DIRS Definitions and rules for building
|
||||
subdirectories</TT>
|
||||
<BR> <TT>RULES_JAVA Definitions and rules for java jars and
|
||||
classes</TT>
|
||||
<BR> <TT>RULES_TOP Rules specific to a <top> dir (uninstall
|
||||
and tar)</TT>
|
||||
<BR> <TT>Sample.Makefile Sample makefile with comments</TT>
|
||||
<BR>
|
||||
</BLOCKQUOTE>
|
||||
<H4> base/configure/os directory - contains os-arch specific definitions</H4>
|
||||
<BLOCKQUOTE>
|
||||
<TT>CONFIG.<host>.<target> Specific host-target build
|
||||
definitions</TT>
|
||||
<BR> <TT>CONFIG.Common.<target> Specific target definitions for all
|
||||
hosts</TT>
|
||||
<BR> <TT>CONFIG.<host>.Common Specific host definitions for all
|
||||
targets</TT>
|
||||
<BR> <TT>CONFIG.UnixCommon.Common Definitions for Unix hosts and all
|
||||
targets</TT>
|
||||
<BR> <TT>CONFIG.Common.UnixCommon Definitions for Unix targets and
|
||||
all hosts</TT>
|
||||
<BR> <TT>CONFIG.Common.vxWorksCommon Specific host definitions for all
|
||||
vx targets</TT>
|
||||
<BR> <TT>CONFIG_COMPAT R3.13 arch compatibility
|
||||
definitions</TT>
|
||||
<BR> <TT>CONFIG_SITE.<host>.<target> Site specific host-target
|
||||
definitions</TT>
|
||||
<BR> <TT>CONFIG_SITE.Common.<target> Site specific target defs for all
|
||||
hosts</TT>
|
||||
<BR> <TT>CONFIG_SITE.<host>.Common Site specific host defs for all
|
||||
targets</TT>
|
||||
<BR>
|
||||
</BLOCKQUOTE>
|
||||
<H4> base/src/tools directory - contains Perl scripts used for the build</H4>
|
||||
<BLOCKQUOTE>
|
||||
<TT>Makefile Makefile for installing the scripts into cfg dir</TT><BR>
|
||||
<TT>convertRelease.pl Performs consistancy checks on RELEASE
|
||||
files</TT>
|
||||
<BR> <TT>cvsclean.pl Remove all .#* files in directory tree</TT>
|
||||
<BR> <TT>dos2unix.pl Converts text file from DOS CR/LF to unix ISO</TT>
|
||||
<BR> <TT>expandvars.pl Tool to expand @VAR@ variables while copying a file</TT>
|
||||
<BR> <TT>filterWarnings.pl Filters warning messages during HP
|
||||
builds</TT>
|
||||
<BR> <TT>fullpathName.pl Returns fullpath name of directory arg</TT>
|
||||
<BR> <TT>installEpics.pl Installs built files into install
|
||||
directories</TT>
|
||||
<BR> <TT>makeIncludeDbd.pl Creates *Include.dbd file from filename
|
||||
args</TT> files
|
||||
<BR> <TT>makeMakefile.pl Creates a Makefile in O.<arch> dirs</TT>
|
||||
<BR> <TT>makeTestfile.pl Generates a test harness $target.t file</TT>
|
||||
<BR> <TT>mkmf.pl Generates dependencies from include
|
||||
stmnts</TT>
|
||||
<BR> <TT>munch.pl Creates a ctdt.c file for vxWorks
|
||||
targets</TT>
|
||||
<BR> <TT>replaceVAR.pl Changes CapFast VAR(xxx) to $(xxx) notation</TT>
|
||||
<BR> <TT>useManifestTool.pl Use MS VC++ version to set usage of Manifest Tool</TT>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H4>base/documentation/README* files</H4>
|
||||
<PRE>
|
||||
README.1st Instructions for setup and building epics base
|
||||
README.html html version of README.1st
|
||||
README.WIN32 Microsoft WIN32 specific instructions
|
||||
README.cxxTemplates Information about C++ templates in EPICS base
|
||||
README.niCpu030 NI cpu030 specific instructions
|
||||
README.darwin Installation notes for Mac OS X (Darwin)
|
||||
RELEASE_NOTES.html Notes on release changes
|
||||
KnownProblems.html List of known problems and workarounds
|
||||
Converting*To*.html Release specific conversion instructions
|
||||
Building*With*.html Release specific build instructions
|
||||
</PRE>
|
||||
|
||||
<H4>base/startup directory - contains scripts to set environment and path</H4>
|
||||
<PRE>
|
||||
EpicsHostArch C shell script to set EPICS_HOST_ARCH env variable
|
||||
EpicsHostArch.pl Perl script to set EPICS_HOST_ARCH env variable
|
||||
Site.profile bourne shell script to set path and env variables
|
||||
Site.cshrc c shell script to set path and env variables
|
||||
borland.bat WIN32 bat file to set borland path and env variables
|
||||
cygwin.bat WIN32 bat file to set cygwin path and env variables
|
||||
win32.bat WIN32 bat file to set path and env variables
|
||||
win32-debug.bat WIN32 debug bat file to set debug path and env variables
|
||||
</PRE>
|
||||
|
||||
<H4>base/configure directory - contains build definitions and rules</H4>
|
||||
<PRE>
|
||||
CONFIG Includes configure files and allows variable overrides
|
||||
CONFIG.CrossCommon Cross build definitions
|
||||
CONFIG.gnuCommon Gnu compiler build definitions for all archs
|
||||
CONFIG_ADDONS Definitions for <osclass> and DEFAULT options
|
||||
CONFIG_BASE EPICS base tool and location definitions
|
||||
CONFIG_BASE_VERSION Definitions for EPICS base version number
|
||||
CONFIG_COMMON Definitions common to all builds
|
||||
CONFIG_ENV Definitions of EPICS environment variables
|
||||
CONFIG_SITE Site specific make defintions
|
||||
CONFIG_SITE_ENV Site defaults for EPICS environment variables
|
||||
MAKEFILE Installs CONFIG* RULES* creates
|
||||
CONFIG_APP_INCLUDE
|
||||
RELEASE Location of external products
|
||||
RULES Includes appropriate rules file
|
||||
RULES.Db Rules for database and database definition files
|
||||
RULES.ioc Rules for application iocBoot/ioc* directory
|
||||
RULES_ARCHS Definitions and rules for building architectures
|
||||
RULES_BUILD Build and install rules and definitions
|
||||
RULES_DIRS Definitions and rules for building subdirectories
|
||||
RULES_JAVA Definitions and rules for java jars and classes
|
||||
RULES_TOP Rules specific to a <top> dir (uninstall and tar)
|
||||
Sample.Makefile Sample makefile with comments
|
||||
</PRE>
|
||||
|
||||
<H4>base/configure/os directory - contains os-arch specific definitions</H4>
|
||||
<PRE>
|
||||
CONFIG.<host>.<target> Specific host-target build definitions
|
||||
CONFIG.Common.<target> Specific target definitions for all hosts
|
||||
CONFIG.<host>.Common Specific host definitions for all targets
|
||||
CONFIG.UnixCommon.Common Definitions for Unix hosts and all targets
|
||||
CONFIG.Common.UnixCommon Definitions for Unix targets and all hosts
|
||||
CONFIG.Common.vxWorksCommon Specific host definitions for all vx targets
|
||||
CONFIG_COMPAT R3.13 arch compatibility definitions
|
||||
CONFIG_SITE.<host>.<target> Site specific host-target definitions
|
||||
CONFIG_SITE.Common.<target> Site specific target defs for all hosts
|
||||
CONFIG_SITE.<host>.Common Site specific host defs for all targets
|
||||
</PRE>
|
||||
|
||||
<H4>base/src/tools directory - contains Perl scripts used for the build</H4>
|
||||
<PRE>
|
||||
Makefile Makefile for installing the scripts into cfg dir
|
||||
convertRelease.pl Performs consistancy checks on RELEASE files
|
||||
cvsclean.pl Remove all .#* files in directory tree
|
||||
dos2unix.pl Converts text file from DOS CR/LF to unix ISO
|
||||
expandvars.pl Tool to expand @VAR@ variables while copying a file
|
||||
filterWarnings.pl Filters warning messages during HP builds
|
||||
fullpathName.pl Returns fullpath name of directory arg
|
||||
installEpics.pl Installs built files into install directories
|
||||
makeIncludeDbd.pl Creates *Include.dbd file from filename args files
|
||||
makeMakefile.pl Creates a Makefile in O.<arch> dirs
|
||||
makeTestfile.pl Generates a test harness $target.t file
|
||||
mkmf.pl Generates dependencies from include stmnts
|
||||
munch.pl Creates a ctdt.c file for vxWorks targets
|
||||
replaceVAR.pl Changes CapFast VAR(xxx) to $(xxx) notation
|
||||
useManifestTool.pl Use MS VC++ version to set usage of Manifest Tool
|
||||
</PRE>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_12"> Building EPICS base (Unix and Win32)</A></H3>
|
||||
<BLOCKQUOTE>
|
||||
|
||||
<H4> Unpack file</H4>
|
||||
<BLOCKQUOTE>
|
||||
Unzip and untar the distribution file. Use WinZip on Windows
|
||||
systems.
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H4>Set environment variables</H4>
|
||||
<BLOCKQUOTE>
|
||||
Files in the base/startup directory have been provided to
|
||||
help set required path and other environment variables .
|
||||
<P><B>EPICS_HOST_ARCH</B>
|
||||
<BR> Before you can build or use EPICS R3.14, the environment variable
|
||||
help set required path and other environment variables.
|
||||
|
||||
<P><B>EPICS_HOST_ARCH</B><BR>
|
||||
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
|
||||
@@ -463,19 +321,22 @@ Files in the base/startup directory have been provided to
|
||||
(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.</P>
|
||||
<P><B>PERLLIB</B>
|
||||
<BR> On WIN32, some versions of Perl require that the environment
|
||||
|
||||
<P><B>PERLLIB</B><BR>
|
||||
On WIN32, some versions of Perl require that the environment
|
||||
variable PERLLIB be set to <perl directory location>.</P>
|
||||
<P><B>PATH</B>
|
||||
<BR> As already mentioned, you must have the perl executable and you may
|
||||
|
||||
<P><B>PATH</B><BR>
|
||||
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 ln, 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 as and ld in your path. On
|
||||
your path, and the C compiler may require as and ld in your path. On
|
||||
solaris systems you need uname in your path.</P>
|
||||
<P><B>LD_LIBRARY_PATH</B>
|
||||
<BR> It is no longer necessary to have LD_LIBRARY_PATH include EPICS
|
||||
|
||||
<P><B>LD_LIBRARY_PATH</B><BR>
|
||||
It is no longer necessary to have LD_LIBRARY_PATH include EPICS
|
||||
directories on a Unix type system. R3.14 shared libraries and
|
||||
executables will contain the full path name to libraries they require.
|
||||
However, if you move the EPICS directories from their build-time
|
||||
@@ -486,72 +347,83 @@ Files in the base/startup directory have been provided to
|
||||
hosts. NOTE: You will still need LD_LIBRARY_PATH for R3.13 extension
|
||||
shared libraries even if the R3.13 extensions are built with R3.14
|
||||
base.</P>
|
||||
<P><B>Win32 PATH</B>
|
||||
<BR> On WIN32 systems, for R3.14.7 and later, it is no longer necessary
|
||||
|
||||
<P><B>Win32 PATH</B><BR>
|
||||
On WIN32 systems, for R3.14.7 and later, it is no longer necessary
|
||||
to add fullpathname to $(INSTALL_LOCATION)/bin/$(EPICS_HOST_ARCH) to
|
||||
your path for finding dlls during EPICS builds. The win32 configure
|
||||
files in base now add this directory to the path definition.</P>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H4>Do site-specific build configuration</H4>
|
||||
<BLOCKQUOTE>
|
||||
<B>Site configuration</B>
|
||||
<BR> To configure EPICS, you may want to modify the default definitions
|
||||
|
||||
<B>Site configuration</B><BR>
|
||||
To configure EPICS, you may want to modify the default definitions
|
||||
in the following files:
|
||||
<BLOCKQUOTE>
|
||||
<TT>configure/CONFIG_SITE
|
||||
Build choices. Specify target archs.<br></TT>
|
||||
<TT>configure/CONFIG_SITE_ENV
|
||||
Environment variable defaults</TT><br>
|
||||
<TT>configure/RELEASE
|
||||
TORNADO2 full path location</TT>
|
||||
</BLOCKQUOTE><B> Host configuration</B>
|
||||
<BR> To configure each host system, you may override the default
|
||||
<PRE>
|
||||
configure/CONFIG_SITE Build choices. Specify target archs.
|
||||
configure/CONFIG_SITE_ENV Environment variable defaults
|
||||
configure/RELEASE TORNADO2 full path location
|
||||
</PRE>
|
||||
|
||||
<B> Host configuration</B><BR>
|
||||
To configure each host system, you may override the default
|
||||
definitions by adding a new file in the configure/os directory with
|
||||
override definitions. The new file should have the same name as the
|
||||
distribution file to be overridden except with CONFIG in the name
|
||||
changed to CONFIG_SITE.<BLOCKQUOTE>
|
||||
<TT>configure/os/CONFIG.<host>.<host>
|
||||
|
||||
Host build settings</TT><BR>
|
||||
<TT>configure/os/CONFIG.<host>.Common
|
||||
|
||||
Host common build settings</TT>
|
||||
</BLOCKQUOTE><B> Target configuration</B>
|
||||
<BR> To configure each target system, you may override the default
|
||||
changed to CONFIG_SITE.
|
||||
|
||||
<PRE>
|
||||
configure/os/CONFIG.<host>.<host> Host build settings
|
||||
configure/os/CONFIG.<host>.Common Host common build settings
|
||||
</PRE>
|
||||
|
||||
<B>Target configuration</B><BR>
|
||||
To configure each target system, you may override the default
|
||||
definitions by adding a new file in the configure/os directory with
|
||||
override definitions. The new file should have the same name as the
|
||||
distribution file to be overridden except with CONFIG in the name
|
||||
replaced by CONFIG_SITE. This step is necessary even if the host system
|
||||
is the only target system.<BLOCKQUOTE>
|
||||
<TT>configure/os/CONFIG.Common.<target>
|
||||
Target common settings</TT><BR>
|
||||
<TT>configure/os/CONFIG.<host>.<target>
|
||||
Host-target settings</TT>
|
||||
</BLOCKQUOTE><B>
|
||||
R3.13 compatibility configuration</B>
|
||||
<BR> To configure EPICS base for building with R3.13 extensions and ioc
|
||||
is the only target system.
|
||||
<PRE>
|
||||
configure/os/CONFIG.Common.<target> Target common settings
|
||||
configure/os/CONFIG.<host>.<target> Host-target settings
|
||||
</PRE>
|
||||
|
||||
<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* files to agree with definitions you made in
|
||||
base/configure and base/configure/os files.
|
||||
</BLOCKQUOTE>
|
||||
<H4><B> Build EPICS base</B></H4>
|
||||
|
||||
<H4>Build EPICS base</H4>
|
||||
<BLOCKQUOTE>After configuring the build you should be able to build
|
||||
EPICS base by issuing the following commands in the distribution's root
|
||||
directory (base)<BLOCKQUOTE><TT>gnumake clean uninstall</TT>
|
||||
<BR> <TT>gnumake</TT></BLOCKQUOTE> The command "gnumake clean uninstall"
|
||||
directory (base):
|
||||
<PRE>
|
||||
gnumake clean uninstall
|
||||
gnumake
|
||||
</PRE>
|
||||
|
||||
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><BR> It is recommended that you do a "gnumake clean uninstall" at the
|
||||
|
||||
<P> It is recommended that you do a "gnumake clean uninstall" at the
|
||||
root directory of an EPICS directory structure before each complete
|
||||
rebuild to ensure that all components will be rebuilt.</BLOCKQUOTE></BLOCKQUOTE>
|
||||
rebuild to ensure that all components will be rebuilt.
|
||||
</BLOCKQUOTE>
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_13"> Example application and extension</A></H3>
|
||||
<BLOCKQUOTE>A perl tool, makeBaseApp.pl is included in the distribution
|
||||
file. This script will create a sample application that can be built
|
||||
and then executed to try out this release of base.
|
||||
|
||||
</BLOCKQUOTE><BLOCKQUOTE>
|
||||
<P>
|
||||
Instructions for building and executing the 3.14 example application
|
||||
can be found in the section "Example Application" of Chapter 2,
|
||||
"Getting Started", in the "IOC Application Developer's Guide" for this
|
||||
@@ -562,14 +434,15 @@ Build choices. Specify target archs.<br></TT>
|
||||
By running the example application as a host-based IOC, you will be
|
||||
able to quickly implement a complete EPICS system and be able to run channel
|
||||
access clients on the host system.
|
||||
</BLOCKQUOTE>
|
||||
<BLOCKQUOTE>
|
||||
|
||||
<P>
|
||||
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.
|
||||
</BLOCKQUOTE>
|
||||
|
||||
<H3><A NAME="0_0_14"> Multiple host platforms</A></H3>
|
||||
<BLOCKQUOTE>You can build using a single EPICS directory structure on
|
||||
multiple host systems and for multiple cross target systems. The
|
||||
@@ -584,7 +457,8 @@ Build choices. Specify target archs.<br></TT>
|
||||
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/c++ cross compiler and target header files and the
|
||||
base/configure/os directory must have the appropriate configure files.</BLOCKQUOTE>
|
||||
</BLOCKQUOTE></BODY>
|
||||
host/target C/C++ cross compiler and target header files and the
|
||||
base/configure/os directory must have the appropriate configure files.
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
@@ -13,6 +13,12 @@
|
||||
<h2 align="center">Changes between 3.14.11 and 3.14.12</h2>
|
||||
<!-- Insert new items immediately below here ... -->
|
||||
|
||||
<h4>Added windows-x64 target</h4>
|
||||
|
||||
<p>64-bit binaries for Microsoft Windows platforms can now be built using the
|
||||
target architecture windows-x64, which is also a valid cross-build target for a
|
||||
win32-x86 host. We do not currently support 64-bit MinGW or Cygwin builds.</p>
|
||||
|
||||
<h4>Deleted osf-alpha targets</h4>
|
||||
|
||||
<p>Kazuro Furukawa has been unable to compile EPICS Base on this target for the
|
||||
|
||||
Reference in New Issue
Block a user