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

Renamed convertRelease target 'STDOUT' to 'releaseTops' and fixed build files.

Browse Source 
Removed the -h option to convertRelease, use $ENV{EPICS_HOST_ARCH} instead.
Reworked variables associated with expandVars to make it simpler to use.
Split EPICS::Utils module into three parts.
Moved code from fullPathName.pl into the new EPICS::Path module.
Changed convertRelease.pl to use new modules.
Added some documentation to RELEASE_NOTES.html
This commit is contained in:
Andrew Johnson
2008-04-03 21:57:16 +00:00
parent 2a9ccaf2c0
commit fb930b6b0e
15 changed files with 616 additions and 495 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
documentation/RELEASE_NOTES.html
View File

@@ -9,10 +9,66 @@
<body lang="en">
<h1 align="center">EPICS Base Release 3.14.x</h1>
<h2 align="center">Changes between 3.14.9 and 3.14.x</h2>
<h2 align="center">Changes between 3.14.9 and 3.14.10</h2>
<!-- Insert new items below here ... -->
<h4>Build System Reorganization</h4>
<p>Several changes have been made to the build system, although these changes
should not affect the contents of <tt>Makefile</tt>s or any applications using
Base. They do however require that the version of GNU Make used be 3.80 (3.81?)
or later. These changes are briefly:</p>
<ul>
<li>
<p>A new tool is provided that expands out <tt>@VAR@</tt> macros. By
default it knows the value of <tt>@TOP@</tt>, <tt>@ARCH@</tt> and any paths
defined in the application's <tt>configure/RELEASE</tt> file, but additional
macros can be defined in the <tt>Makefile</tt> that uses it by adding to the
<tt>EXPAND_VARS</tt> macro like the example following, which creates an
<tt>@EXE@</tt> macro that expands out to <tt>.exe</tt> on windows and to
nothing on other platforms:</p>
<pre> EXPAND_VARS += EXE=$(EXE)</pre>
<p>Files that contain <tt>@VAR@</tt> macros to be substituted must have an
at sign <tt><b>@</b></tt> as the last character of their name and be listed
in the <tt>EXPAND</tt> variable of their <tt>Makefile</tt>. The expanded
file will have the same name as the original with the <tt><b>@</b></tt>
suffix removed, and is then available for compiling or installing using any
other build mechanism.</p>
</li>
<li>
<p>Support has been added for installing Perl library modules. The
<tt>Makefile</tt> variable <tt>PERL_MODULES</tt> can be set to a list of
names of files to be installed into the <tt>$(TOP)/lib/perl</tt> directory.
The above macro expansion facility can then be used in perl programs that
use these libraries to set the perl search path to include that directory.
The syntax for this is as follows:</p>
<pre> use lib '@TOP@/lib/perl';
use MyModule;</pre>
<p>The filenames listed in <tt>PERL_MODULES</tt> can include subdirectory
path components and the build system will preserve these in the installed
result.</p>
</li>
<li>The Perl scripts that were in <tt>configure/tools</tt> are now found in
the new <tt>src/tools</tt> directory, and get installed into the appropriate
<tt>bin/<i>hostarch</i></tt> directory at build time. Some of these scripts
are no longer required and have been removed, and others are being modified
to make them more modular, extracting common routines into perl library
modules.</li>
<li>The generated files that were created by running make in the
<tt>configure</tt> directory are no longer required, having been replaced by
additional mechanisms inside the build system files. This removes a common
source of build problems.</li>
</ul>
<h4>Access security configuration files</h4>
<p>Rules and macros were added for creating an *.acf file, access security