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

Updates for R3.14.0.beta1.

Browse Source
This commit is contained in:
Janet B. Anderson
2001-10-02 14:02:23 +00:00
parent e8d24da299
commit ba3be45400
3 changed files with 32 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.WIN32
+14 -14
View File
@@ -1,5 +1,5 @@
Compiling EPICS and Building IOC Applications on WIN32 (Windows95/NT)
Compiling EPICS and Building IOC Applications on win32-x86 (Windows95/NT)
---------------------------------------------------------------------
Original port of EPICS base build system to WIN32 (Windows95/NT)
@@ -11,9 +11,9 @@ please mail questions, comments, corrections, additional examples, etc
0) what you will get
--------------------
Right now this port of EPICS to WIN32 should allow you to
Right now this port of EPICS to win32-x86 should allow you to
* compile almost all of EPICS base using {Tornado, MS Visual C, perl,
* compile all of EPICS base using {Tornado, MS Visual C, perl,
GNU make} (only {MS Visual C, perl, GNU make} if you prefer
to compile only the host portions of EPICS base).
* load EPICS on an IOC (486, pentium, 68k, ...),
@@ -23,16 +23,16 @@ Right now this port of EPICS to WIN32 should allow you to
* build and use ca.dll on NT or Win95 to access all IOCs,
as well as the Com-library, gdd-library, cas-library,
and all other EPICS base libraries as DLLs.
* build gdd, cas and a demo of the new portable CA server on WIN32.
To build only for WIN32 and not cross compile for IOC development type
"make host" or in your config files set "CROSS_COMPILER_HOST_ARCHS=void"
* build gdd, cas and a demo of the new portable CA server on win32-x86.
To build only for win32-x86 and not cross compile for IOC development type
"make win32-x86" or in your configure/CONFIG_SITE file set
"CROSS_COMPILER_HOST_ARCHS="
1) see what you have
--------------------
To compile EPICS on WIN32, we need
To compile EPICS on win32-x86, we need
WindRiver System's Tornado (used: 1.0) (not required if host only build)
Microsoft's Visual C/C++ (used: 6.0) (borland C++ rumored to work also)
@@ -51,7 +51,7 @@ If you cannot/don't want to find them, contact me, please!
(Setting env. vars. is different: for NT, use Settings/System,
for Win95 use autoexec.bat)
When setting paths in the EPICS CONFIG files for WIN32 the following
When setting paths in the EPICS CONFIG files for win32-x86 the following
are hints in case you have trouble. You should not need to worry about
this unless you type a path into one of the EPICS config files that
includes a "\". In most situations gnu make, windows NT, the MS compiler,
@@ -66,7 +66,7 @@ and the MS linker will accept "/" and this will result in less trouble.
a "\ " (this is because GNU make treats all " " separated
input as independent tokens in the input stream.
** WIN32 will generally allow "/" and "\" interchangeably in file paths,
** win32-x86 will generally allow "/" and "\" interchangeably in file paths,
but the DOS shell only accepts "\".
** Certain command line utilities such as the MS linker are known to in rare
@@ -75,7 +75,7 @@ and the MS linker will accept "/" and this will result in less trouble.
the bulk of our experience indicates that this is not the necessary.
Your path should include:
- The EPICS-binaries that we are about to build in <EPICS>base/bin/WIN32
- The EPICS-binaries that we are about to build in <EPICS>base/bin/win32-x86
- The System (for me it's in NT40...)
- The MS Visual C compiler binaries
@@ -108,7 +108,7 @@ include=c:\msdev\include;c:\msdev\mfc\include
lib=c:\msdev\lib;c:\msdev\mfc\lib
Select host arch to build:
HOST_ARCH=WIN32 (used by the make system)
EPICS_HOST_ARCH=win32-x86 (used by the make system)
Set the "TMP" environment variable if you need to specify where
temporary files are created.
@@ -139,7 +139,7 @@ Prepare apx. 2 ltr. Tee and type:
Watch for errors and send them to me.
Known problems:
* gnumake seems to be faster than WIN32 sometimes
* gnumake seems to be faster than win32-x86 sometimes
which results in warnings/errors like
"file has modification date in the future"
for newly created things.
@@ -150,7 +150,7 @@ Known problems:
WIN32 is WIN32, not win32. Gnumake fails
if e.g. base/src/include/os/WIN32 is ...win32.
4) Creating EPICS IOC applications under WIN32
4) Creating EPICS IOC applications under win32-x86
o create application development folder
READMEbuildingR3.13AppsWithR3.14.html
+16 -12
View File
@@ -5,7 +5,7 @@
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 9">
<meta name="Originator" content="Microsoft Word 9">
<meta name="GENERATOR" content="Mozilla/4.76 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]">
<meta name="GENERATOR" content="Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u) [Netscape]">
<title>Instruction on building existing R3</title>
<link rel=File-List href="./READMEbuildingR3.13AppsWithR3.14_files/filelist.xml">
<!--[if gte mso 9]><xml>
@@ -85,10 +85,10 @@ div.Section1
<center>
<h2>
Building EPICS R3.13 applications with R3.14.0alpha3 base</h2></center>
Building EPICS R3.13 applications with R3.14.0beta1 base</h2></center>
<p><br>This document describes how to modify a R3.13 vxWorks application
so that it builds with release R3.14.0alpha3.&nbsp; It describes an easy
so that it builds with release R3.14.0beta1.&nbsp; It describes an easy
way to modify applications subject to the following restrictions:
<ul>
<li>
@@ -142,19 +142,22 @@ files.</blockquote>
State Notation Language changes</h3>
<blockquote>snc is no longer in base. If snc is used in your application,
you must download and build the seq module with baseR3.14.0alpha3. See
the Application Developer's Guide to see how to build sequence programs.</blockquote>
you must download and build the seq module with baseR3.14.0beta1. See the
Application Developer's Guide to see how to build sequence programs.</blockquote>
<blockquote>Change
<pre>INSTALLS=seq</pre>
to
<pre>LIBOBJS = $(SEQ_BIN)/seqLibrary.o</pre>
<pre>LIBOBJS += $(SEQ_BIN)/seqLibrary.o</pre>
<p><br>in application src/Makefile.Vx files to link seq library into your
application library,.
<br>Also add
<pre>SEQ=&lt;full path to seq module directory></pre>
to config/RELEASE.</blockquote>
to config/RELEASE.
<br>Also remove
<pre>ld &lt; seq</pre>
from the st.cmd files in the iocBoot subdirectories.</blockquote>
<h3>
iocCore changes</h3>
@@ -163,7 +166,7 @@ iocCore changes</h3>
<br>Change
<pre>INSTALLS=iocCore</pre>
to
<pre>LIBOBJS = $(EPICS_BASE_BIN)/iocCoreLibrary.o</pre>
<pre>LIBOBJS += $(EPICS_BASE_BIN)/iocCoreLibrary.o</pre>
in your application src/Makefile.Vx files .
<br>Also remove
<pre>ld &lt; iocCore</pre>
@@ -239,7 +242,7 @@ application.</blockquote>
Hardware support changes</h3>
<blockquote>All hardware support (dev, drv and dbd files) has been unbundled
from base R3.14. This support includes the files <tt>symb.dbd, drvHp1404a.o,
from base R3.14. This support includes the files <tt>symb, symb.dbd, drvHp1404a.o,
drvEpvxiMsg.o, and drvEpvxi.o</tt>.&nbsp; If they are not used in your
application, comment out references to these files in base.dbd and baseLIBOBJS.
<p>Hardware support files now exist as separate modules available for download
@@ -282,13 +285,14 @@ and change line:
<pre>@$(DBLOADTEMPLATE) $&lt; > $@</pre>
to
<pre>@$(MSI) $&lt; > $@</pre>
Also add the definition
Also, if dbLoadTemplate was used by your application,&nbsp; add the definition
<blockquote>
<pre>EPICS_EXTENSIONS=&lt;full path name to epics extensions directory></pre>
</blockquote>
to your application config/RELEASE file.</blockquote>
depends changes
<p>&nbsp;&nbsp;&nbsp;&nbsp; Remove any SRCS.c and SRCS.cc definitions.
Depends no longer uses these definitions.
<p>&nbsp;&nbsp;&nbsp;&nbsp; Remove any SRCS.c and SRCS.cc definitions in
your application src/Makefile..*files. The depends rule no longer uses
these definitions.
</body>
</html>
READMEconvertingR3.14.0alpha2AppsTobeta1.html
+2 -2
View File
@@ -9,10 +9,10 @@
<center>
<h2>
Converting an EPICS R3.14.0alpha2 application to alpha3</h2></center>
Converting an EPICS R3.14.0alpha2 application to beta1</h2></center>
<p><br>This document describes how to convert a R3.14.0alpha2 vxWorks application
so that it builds with release R3.14.0alpha3.
so that it builds with release R3.14.0beta1.
<h3>
Gnumake clean uninstall</h3>