[Gd-chatter] r10728 - in trunk/mps: . code manual/reference procedure/release-build procedure/version-create
housel at gwydiondylan.org
housel at gwydiondylan.org
Thu May 11 21:29:21 CEST 2006
Author: housel
Date: Thu May 11 21:29:18 2006
New Revision: 10728
Modified:
trunk/mps/code/version.c
trunk/mps/index.html
trunk/mps/manual/reference/index.html
trunk/mps/procedure/release-build/index.html
trunk/mps/procedure/version-create/index.html
trunk/mps/readme.txt
Log:
Job: mps
Update to latest (post-1.106.1) version.
Modified: trunk/mps/code/version.c
==============================================================================
--- trunk/mps/code/version.c (original)
+++ trunk/mps/code/version.c Thu May 11 21:29:18 2006
@@ -1,7 +1,8 @@
/* version.c: VERSION INSPECTION
*
- * $Id: //info.ravenbrook.com/project/mps/master/code/version.c#10 $
- * Copyright (c) 2001 Ravenbrook Limited. See end of file for license.
+ * $Id: //info.ravenbrook.com/project/mps/master/code/version.c#11 $
+ * Copyright (c) 2001, 2006 Ravenbrook Limited.
+ * See end of file for license.
*
* PURPOSE
*
@@ -16,17 +17,19 @@
#include "mpm.h"
-SRCID(version, "$Id: //info.ravenbrook.com/project/mps/master/code/version.c#10 $");
+SRCID(version, "$Id: //info.ravenbrook.com/project/mps/master/code/version.c#11 $");
/* MPS_RELEASE -- the release name
*
* .release: When making a new release, change the expansion of
- * MPS_RELEASE to be a string of the form "release.dylan.crow.2" or
+ * MPS_RELEASE to be a string of the form "release/1.106.1" or
* whatever.
+ *
+ * (Note: before 2006-02-01 the style was "release.epcore.chub")
*/
-#define MPS_RELEASE "release.epcore.chub"
+#define MPS_RELEASE "release/1.106.2"
/* MPSCopyrightNotice -- copyright notice for the binary
@@ -36,13 +39,15 @@
*/
char MPSCopyrightNotice[] =
- "Portions copyright (c) 2002 Ravenbrook Limited and Global Graphics Software.";
+ "Portions copyright (c) 2006 Ravenbrook Limited and Global Graphics Software.";
/* MPSVersion -- return version string
*
* The value of MPSVersion is a declared object comprising the
- * concatenation of all the version info.
+ * concatenation of all the version info. The "@(#)" prefix
+ * is the convention used by the BSD Unix command what(1);
+ * see also guide.mps.version.
*/
char MPSVersionString[] =
@@ -58,7 +63,8 @@
/* C. COPYRIGHT AND LICENSE
*
- * Copyright (C) 2001-2002 Ravenbrook Limited <http://www.ravenbrook.com/>.
+ * Copyright (C) 2001-2002, 2006 Ravenbrook Limited
+ * <http://www.ravenbrook.com/>.
* All rights reserved. This is an open source license. Contact
* Ravenbrook for commercial licensing options.
*
Modified: trunk/mps/index.html
==============================================================================
--- trunk/mps/index.html (original)
+++ trunk/mps/index.html Thu May 11 21:29:18 2006
@@ -91,6 +91,14 @@
<tr valign="top">
+ <td> <code> <a href="example/">example/</a> </code> </td>
+
+ <td> Example code -- how to write code that uses the MPS. </td>
+
+</tr>
+
+<tr valign="top">
+
<td> <code> <a href="manual/">manual/</a> </code> </td>
<td> Product manuals. </td>
@@ -224,6 +232,16 @@
</tr>
+<tr valign="top">
+
+ <td> 2006-04-14 </td>
+
+ <td> <a href="mailto:rhsk at ravenbrook.com">RHSK</a> </td>
+
+ <td> Added <code>example/</code>. </td>
+
+</tr>
+
</table>
@@ -250,7 +268,7 @@
<div align="center">
-<p><code>$Id: //info.ravenbrook.com/project/mps/master/index.html#6 $</code></p>
+<p><code>$Id: //info.ravenbrook.com/project/mps/master/index.html#7 $</code></p>
<p>
<a href="/">Ravenbrook</a> /
Modified: trunk/mps/manual/reference/index.html
==============================================================================
--- trunk/mps/manual/reference/index.html (original)
+++ trunk/mps/manual/reference/index.html Thu May 11 21:29:18 2006
@@ -1,6 +1,8 @@
-<?xml version="1.0"?>
+<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd">
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transisitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -913,7 +915,7 @@
<code><a href="#MPS_FIX2">MPS_FIX2</a></code></p>
-<h3>constant <code><a id="MPS_RES_LIMIT" name="MPS_RES_LIMIT">MPS_RES_LIMIT</a></code></h3>
+<h3>constant <code><a id="MPS_RES_LIMIT_detailed" name="MPS_RES_LIMIT_detailed">MPS_RES_LIMIT</a></code></h3>
<h4>Name</h4>
@@ -962,7 +964,7 @@
<code><a href="#mps_res_t">mps_res_t</a></code></p>
-<h3>constant <code><a id="MPS_RES_MEMORY" name="MPS_RES_MEMORY">MPS_RES_MEMORY</a></code></h3>
+<h3>constant <code><a id="MPS_RES_MEMORY_detailed" name="MPS_RES_MEMORY_detailed">MPS_RES_MEMORY</a></code></h3>
<h4>Name</h4>
@@ -1019,7 +1021,7 @@
href="#MPS_RES_COMMIT_LIMIT">MPS_RES_COMMIT_LIMIT</a></code></p>
-<h3><code><a id="MPS_RES_PARAM" name="MPS_RES_PARAM">MPS_RES_PARAM</a></code></h3>
+<h3>constant <code><a id="MPS_RES_PARAM_detailed" name="MPS_RES_PARAM_detailed">MPS_RES_PARAM</a></code></h3>
<h4>Name</h4>
@@ -3256,9 +3258,9 @@
<h4>Description</h4>
-<p>This function is used to get hold of the virtual memory arena class, for the purpose ofpassing it to <code><a href="#mps_arena_create">mps_arena_create</a></code>. The VM arenas use the OS virtual memory interfaces toallocate memory. The chief consequence of this is that the arena can manage many more virtualaddresses than it needs to commit memory to. This gives it flexibility as to where to place objects,which reduces fragmentation and helps make garbage collection more efficient.</p>
+<p>This function is used to get hold of the virtual memory arena class, for the purpose of passing it to <code><a href="#mps_arena_create">mps_arena_create</a></code>. The VM arenas use the OS virtual memory interfaces toallocate memory. The chief consequence of this is that the arena can manage many more virtual addresses than it needs to commit memory to. This gives it flexibility as to where to place objects, which reduces fragmentation and helps make garbage collection more efficient.</p>
-<p>This class is similar to <code><a href="#mps_arena_class_vmnz">mps_arena_class_vmnz</a></code> but uses a more complex placementpolicy, which is more suited to copying garbage collection.</p>
+<p>This class is similar to <code><a href="#mps_arena_class_vmnz">mps_arena_class_vmnz</a></code> but uses a more complex placement policy, which is more suited to copying garbage collection.</p>
<h4>Example</h4>
@@ -4110,7 +4112,7 @@
<h4>Returned Values</h4>
<p>A boolean. Returns true if the address is managed by the arena,
-false otherwise.
+false otherwise.</p>
<h4>Resources</h4>
@@ -4153,7 +4155,7 @@
<p>
<code><a href="#mps_arena_clamp">mps_arena_park</a> used to park an
-arena</code>,
+arena</code></p>
<h4>Notes</h4>
@@ -4786,7 +4788,7 @@
href="#mps_arena_unsafe_restore_protection">mps_arena_unsafe_restore_protection</a></code>
must not be called - simply call <code><a
href="#mps_arena_release">mps_arena_release</a></code> to continue normal
-collections</a>.
+collections.
</p>
<p>
@@ -6929,7 +6931,7 @@
function to all objects on the heap, see
<code><a
href="#mps_arena_formatted_objects_walk">mps_arena_formatted_objects_walk</a></code>
-for details.
+for details.</p>
<h4>Example</h4>
@@ -8740,9 +8742,9 @@
<p><code><a id="MPS_RES_RESOURCE" name="MPS_RES_RESOURCE">MPS_RES_RESOURCE</a></code>: A needed resource could not be obtained. Which resource, depends on thecall. Compare with <code><a href="#MPS_RES_MEMORY">MPS_RES_MEMORY</a></code>, which is a special case of this.</p>
-<p><code><a id="MPS_RES_MEMORY" name="MPS_RES_MEMORY">MPS_RES_MEMORY</a></code>: Needed memory (committed memory, not address space) could not be obtained.</p>
+<p><code><a id="MPS_RES_MEMORY" name="MPS_RES_MEMORY">MPS_RES_MEMORY</a></code>: Needed memory (committed memory, not address space) could not be obtained. (A <a href="#MPS_RES_MEMORY_detailed">more detailed explanation</a>).</p>
-<p><code><a id="MPS_RES_LIMIT" name="MPS_RES_LIMIT">MPS_RES_LIMIT</a></code>: An internal limitation was reached. For example, the maximum number ofsomething was reached.</p>
+<p><code><a id="MPS_RES_LIMIT" name="MPS_RES_LIMIT">MPS_RES_LIMIT</a></code>: An internal limitation was reached. For example, the maximum number ofsomething was reached. (A <a href="#MPS_RES_LIMIT_detailed">more detailed explanation</a>).</p>
<p><code><a id="MPS_RES_UNIMPL" name="MPS_RES_UNIMPL">MPS_RES_UNIMPL</a></code>: The operation, or some vital part of it, is unimplemented. This might bereturned by functions that are no longer supported, or by operations that are included for futureexpansion, but not yet supported.</p>
@@ -8750,7 +8752,7 @@
<p><code><a id="MPS_RES_COMMIT_LIMIT" name="MPS_RES_COMMIT_LIMIT">MPS_RES_COMMIT_LIMIT</a></code>: The arena's commit limit would have been exceeded as a result of(explicit or implicit) allocation. See protocol.arena.commit.</p>
-<p><code><a id="MPS_RES_PARAM" name="MPS_RES_PARAM">MPS_RES_PARAM</a></code>: A parameter of the operation was invalid.</p>
+<p><code><a id="MPS_RES_PARAM" name="MPS_RES_PARAM">MPS_RES_PARAM</a></code>: A parameter of the operation was invalid. (A <a href="#MPS_RES_PARAM_detailed">more detailed explanation</a>).</p>
<h4>A</h4>
@@ -9081,7 +9083,7 @@
void InitThread(ThreadLocals *thr)
{
/* This is a hack to find the bottom of the stack. */
- void *stackBottom=&stackBottom;
+ void *stackBottom=&stackBottom;
mps_thread_reg(&thr->thread, arena);
mps_root_create_reg(&thr->mmRoot, arena, MPS_RANK_AMBIG, (mps_rm_t) 0,
@@ -9971,7 +9973,7 @@
void InitThread(ThreadLocals *thr)
{
/* This is a hack to find the bottom of the stack. */
- void *stackBottom=&stackBottom;
+ void *stackBottom=&stackBottom;
mps_thread_reg(&thr->thread, arena);
mps_root_create_reg(&thr->mmRoot, arena, MPS_RANK_AMBIG, (mps_rm_t)0,
@@ -10539,7 +10541,7 @@
<div align="center">
-<p><code>$Id: //info.ravenbrook.com/project/mps/master/manual/reference/index.html#7 $</code></p>
+<p><code>$Id: //info.ravenbrook.com/project/mps/master/manual/reference/index.html#9 $</code></p>
<p>
<a href="/">Ravenbrook</a> /
Modified: trunk/mps/procedure/release-build/index.html
==============================================================================
--- trunk/mps/procedure/release-build/index.html (original)
+++ trunk/mps/procedure/release-build/index.html Thu May 11 21:29:18 2006
@@ -42,7 +42,9 @@
<p> This is the procedure for building a generic release of the Memory Pool System (an "mps-kit") from the version sources. </p>
-<p> The readership of this document is anyone developing the integration. </p>
+<p> The intended readership of this document is Ravenbrook development staff.
+ (If you are a user of the MPS, and want to build object code from
+ an mps-kit, please see the readme.txt file in the kit). </p>
<p> This document is not confidential. </p>
@@ -57,7 +59,7 @@
<ol>
-<li><p> Choose a release name of the form "VERSION.N" (for example,
+<li><p> Choose a RELEASE name of the form "VERSION.N" (for example,
0.3.0). VERSION is the number of the version you're releasing. N is the
first unused release number (starting at zero). Look in the index of
releases (release/index.html) for existing release numbers for your
@@ -67,16 +69,25 @@
contains an up-to-date description of the release you intend to build
and the correct release name. </p> </li>
-<li><p> [At this point the procedure should tell you to check
-<code>version/<i>VERSION</i>/code/version.c</code>, and whether and how
-to modify it, but currently it does not. It may help to look at
-<code>version/<i>VERSION</i>/design/version-library/index.html</code>.
-RHSK 2005-10-31] </p> </li>
+<li><p> In
+ <code>version/<i>VERSION</i>/code/version.c</code>,
+ set
+ <code>MPS_RELEASE</code>
+ to the correct value (see the rules in the comments),
+ and check strings that contain copyright dates, etc.
+</p> </li>
+
+<li><p> Please update
+ <code>version/<i>VERSION</i>/example/hello-world/index.txt</code>,
+ so that it works with the RELEASE you are creating
+ (eg. 1.106.1 → 1.106.2).
+</p> </li>
+
+<li><p> <strong>Submit <code>readme.txt</code>,
+<code>version.c</code>, and other changed files
+to Perforce before you continue.</strong> </p></li>
-<li><p> <strong>Submit <code>readme.txt</code> to Perforce
-before you continue.</strong> </p></li>
-
-<li><p> Determine the changelevel at which you're going to make the
+<li><p> Determine the CHANGELEVEL at which you're going to make the
release. This will usually be the latest submitted changelevel on the
version branch; to get it, use p4 changes with a max of 1 (one):</p> <blockquote> <code>p4 changes -m 1
version/VERSION/...</code> </blockquote> </li>
@@ -92,7 +103,7 @@
<li>
- <p> Sync the version sources to the changelevel you determined in step 2.1. Sync the version sources to a clean area of the disk, to be sure that there are no extraneous files around. </p>
+ <p> Sync the version sources to the CHANGELEVEL you determined in step 2.1. Sync the version sources to a clean area of the disk, to be sure that there are no extraneous files around. </p>
<blockquote> <code>
p4 sync version/VERSION/...#none <br />
@@ -127,7 +138,7 @@
</li>
<li> <p> Submit the tarball and the readme.txt file to Perforce with
-the comment "Adding the MPS Kit tarball and readme.txt file for
+the comment "MPS: adding the MPS Kit tarball and readme.txt file for
release RELEASE." </p> </li>
</ol>
@@ -139,13 +150,27 @@
<ol>
-<li> <p> Sync the version sources to the changelevel you determined in step 2.1. Sync the version sources to a clean area of the disk, to be sure that there are no extraneous files around. </p> </li>
+<li> <p> Sync the version sources to the CHANGELEVEL you determined in step 2.1. Sync the version sources to a clean area of the disk, to be sure that there are no extraneous files around. </p> </li>
+
+<li> <p> Using the Windows file-browser, copy the version/VERSION directory, paste a copy, and rename it mps-kit-RELEASE. </p></li>
+
+<li> <p> Use the Info-ZIP command-line utility "zip" to create a new archive of these files, called "mps-kit-RELEASE.zip" in the directory "release/RELEASE": </p>
+ <blockquote> <pre><code>zip -r release\RELEASE\mps-kit-RELEASE.zip mps-kit-RELEASE</code></pre> </blockquote>
+</li>
-<li> <p> Launch WinZip and create a new archive called "mps-kit-RELEASE.zip" in the directory "release/RELEASE". Add the MPS sources by selecting "version/VERSION" and turning on "Include subfolders" option. </p> </li>
+<li> <p> Make a self-extracting archive called "mps-kit-RELEASE.exe" from "mps-kit-RELEASE.zip" (in the same directory). The approved way to do this is to prepend the "unzipsfx.exe" extractor (here presumed to be "C:\local\bin\unzipsfx.exe"), and then adjust the offsets in the resulting file: </p>
+ <blockquote> <pre><code>copy /b C:\local\bin\unzipsfx.exe+release\RELEASE\mps-kit-RELEASE.zip release\RELEASE\mps-kit-RELEASE.exe
+zip -A release\RELEASE\mps-kit-RELEASE.exe
+</code></pre> </blockquote>
+</li>
-<li> <p> Make a self-extracting archive called "mps-kit-RELEASE.exe" from "mps-kit-RELEASE.zip" (in the same directory), by selcting Actions → Make .EXE File. </p> </li>
+<li> <p> You can check both archives like this: </p>
+ <blockquote> <pre><code>unzip -tq release\RELEASE\mps-kit-RELEASE.zip
+unzip -tq release\RELEASE\mps-kit-RELEASE.exe
+</code></pre> </blockquote>
+</li>
-<li> <p> Add the self-extracting archive and the zip file to Perforce with the comment "Adding the MPS Kit zip file for release RELEASE." </p> </li>
+<li> <p> Add the zip file and the self-extracting archive to Perforce with the comment "MPS: adding the MPS Kit zip file for release RELEASE." </p> </li>
</ol>
@@ -167,11 +192,29 @@
the release changelevel to the <code>releases</code> table, so that the
correct set of known and fixed issues can be derived. </p></li>
-<li><p> Submit these changes with the comment "Registered release
+<li><p> Submit these changes with the comment "MPS: registered release
RELEASE." </p></li>
-<li><p> Inform the project manager and staff by e-mail to <a
-href="mailto:mps-staff at ravenbrook.com">mps-staff at ravenbrook.com</a>. </p></li>
+<li>
+ <p>
+ Edit the main MPS Project index page at
+ <code>//info.ravenbrook.com/project/mps/index.html</code>,
+ to refer to the new release:
+ </p>
+ <ul>
+ <li> update links to 'the latest release' or
+ 'download' (important);
+ </li>
+ <li> consider updating the 'project status' section. </li>
+ </ul>
+</li>
+
+<li><p>
+ Inform the project manager and staff by e-mail to <a
+ href="mailto:mps-staff at ravenbrook.com">mps-staff at ravenbrook.com</a>.
+ Consider announcing the new release by e-mail to
+ <a href="mailto:mps-discussion at ravenbrook.com">mps-discussion at ravenbrook.com</a>.
+</p></li>
</ol>
@@ -234,12 +277,42 @@
</tr>
+<tr valign="top">
+
+ <td>2005-10-06..31</td>
+
+ <td><a href="mailto:rhsk at ravenbrook.com">RHSK</a></td>
+
+ <td>Clarify this procedure is for general mps-kit releases; correct cp -r to -R. Add: check version.c.</td>
+
+</tr>
+
+<tr valign="top">
+
+ <td>2006-01-19..30</td>
+
+ <td><a href="mailto:rhsk at ravenbrook.com">RHSK</a></td>
+
+ <td>Correct readership statement, and direct MPS users to the mps-kit readme.</td>
+
+</tr>
+
+<tr valign="top">
+
+ <td>2006-02-16</td>
+
+ <td><a href="mailto:rhsk at ravenbrook.com">RHSK</a></td>
+
+ <td>Use Info-ZIP (free) for Windows archives, not WinZip.</td>
+
+</tr>
+
</table>
<h2><a id="section-C" name="section-C">C. Copyright and License</a></h2>
-<p> This document is copyright © 2002 <a href="http://www.ravenbrook.com/">Ravenbrook Limited</a>. All rights reserved. This is an open source license. Contact Ravenbrook for commercial licensing options. </p>
+<p> This document is copyright © 2002, 2005-2006 <a href="http://www.ravenbrook.com/">Ravenbrook Limited</a>. All rights reserved. This is an open source license. Contact Ravenbrook for commercial licensing options. </p>
<p> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: </p>
@@ -260,7 +333,7 @@
<div align="center">
-<p><code>$Id: //info.ravenbrook.com/project/mps/master/procedure/release-build/index.html#6 $</code></p>
+<p><code>$Id: //info.ravenbrook.com/project/mps/master/procedure/release-build/index.html#11 $</code></p>
<p>
<a href="/">Ravenbrook</a> /
Modified: trunk/mps/procedure/version-create/index.html
==============================================================================
--- trunk/mps/procedure/version-create/index.html (original)
+++ trunk/mps/procedure/version-create/index.html Thu May 11 21:29:18 2006
@@ -53,6 +53,7 @@
"of the Master version" -> "of Version A.BBB"
"Master" -> "Version A.BBB"
Less importantly, edit various other files. See change 30260.
+Please do edit version/A.BBB/example/hello-world/index.txt.
7. Do an empty-integrate of these changes back on to the masters, so P4 thinks it's done and doesn't keep suggesting it:
p4 integrate -r -b mps/version/A.BBB <Files Edited Master->Version>
@@ -62,9 +63,9 @@
COPYRIGHT AND LICENSE
-Copyright (C) 2005 Ravenbrook Limited <http://www.ravenbrook.com/>.
-All rights reserved. This is an open source license. Contact
-Ravenbrook for commercial licensing options.
+Copyright (C) 2005-2006 Ravenbrook Limited. All rights reserved.
+<http://www.ravenbrook.com/>. This is an open source license.
+Contact Ravenbrook for commercial licensing options.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
@@ -100,4 +101,4 @@
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-$Id: //info.ravenbrook.com/project/mps/master/procedure/version-create/index.txt#5 $
+$Id: //info.ravenbrook.com/project/mps/master/procedure/version-create/index.txt#6 $
Modified: trunk/mps/readme.txt
==============================================================================
--- trunk/mps/readme.txt (original)
+++ trunk/mps/readme.txt Thu May 11 21:29:18 2006
@@ -1,19 +1,17 @@
MEMORY POOL SYSTEM KIT README
-Richard Brooksby, Ravenbrook Limited, 2002-05-20
-
-
CONTENTS
1. Introduction
- 2. Getting started
- 3. The structure of the kit
- 4. Developing using the kit
- 5. Testing
- 6. Building and testing a release
- 7. Contributing your work
- 8. Getting help
- 9. Licensing
+ 2. What's new; status
+ 3. Getting started
+ 4. The structure of the kit
+ 5. Developing using the kit
+ 6. Testing
+ 7. Building and testing a release
+ 8. Contributing your work
+ 9. Getting help
+ 10. Licensing
A. References
B. Document history
C. Copyright and license
@@ -21,7 +19,7 @@
1. INTRODUCTION
-This is the Memory Pool System Kit -- a compelete set of sources for
+This is the Memory Pool System Kit -- a complete set of sources for
using, modifying, and adapting the MPS.
The Memory Pool System (MPS) is a very general, adaptable, flexible,
@@ -48,26 +46,70 @@
This document is not confidential.
-2. GETTING STARTED
+2. WHAT'S NEW; STATUS
+
+(In Master sources, this is a good place to accumulate a succinct
+record of changes. In a release of the MPS-Kit, this section becomes
+the summary of what is new for that release.)
+
+This is release 1.106.2, made on 2006-04-11.
+
+Changes from release 1.106.1:
+
+No functional changes to MPS implementation code.
+
+Fixed <http://www.ravenbrook.com/project/mps/issue/job001352/>
+ - the "mps.a" library does not (now) contain plinth files;
+ - therefore, if your MPS client code needs the example plinth
+ ("mpsplan.a"), you must link with it explicitly to obtain
+ _mps_lib_assert_fail, _mps_clock, etc;
+ - the default "all" build now succeeds on Unix-like platforms
+ (in 1.106.1 the "all" build only worked on Mac OS X).
+
+Fixed <http://www.ravenbrook.com/project/mps/issue/job000605/>
+Fixed <http://www.ravenbrook.com/project/mps/issue/job001366/>
+ - the default Windows "all" build now works with Visual C++ 6.0.
+
+Work on <http://www.ravenbrook.com/project/mps/issue/job001365/>
+ - hopefully fixed some build problems with Visual C++ 7.0.
+
+Fixed <http://www.ravenbrook.com/project/mps/issue/job001367/>
+ - there is a "hello-world" example of using the MPS, in:
+ example/hello-world/index.txt
+
+See:
+ <http://www.ravenbrook.com/project/mps/release/>
+for further details of this release (including defects found), and
+details of earlier and later releases.
+
+For more information about the status and progress of the MPS project,
+consult the project home-page: <http://www.ravenbrook.com/project/mps/>.
+
+
+3. GETTING STARTED
The MPS Kit is a complete set of sources and documentation to enable
third parties to use, modify, and adapt the MPS.
For Windows, the kit is distributed as the self-extracting archive
-"mps-kit-1.100.1.exe", and also as the ZIP archive
-"mps-kit-1.100.1.zip", which may be unpacked using WinZip.
+"mps-kit-1.106.2.exe", and also as the ZIP archive
+"mps-kit-1.106.2.zip", which may be unpacked using WinZip.
For Unix and Mac OS X, the integration kit is distributed as the tarball
-"mps-kit-1.100.1.tar.gz". Unpack it using the command "gunzip -c
-mps-kit-1.100.1.tar.gz | tar xvf -", or by dropping the file onto
+"mps-kit-1.106.2.tar.gz". Unpack it using the command "gunzip -c
+mps-kit-1.106.2.tar.gz | tar xvf -", or by dropping the file onto
StuffIt Expander under Mac OS X.
The top-level file "index.html" in the sources indexes many other files,
and is a good place to start. You should read the user manuals and the
high level design documents.
+A quick start to writing code that uses the MPS is the "hello-world"
+example:
+ example/hello-world/index.txt
+
-3. THE STRUCTURE OF THE KIT
+4. THE STRUCTURE OF THE KIT
The Integration Kit is a copy of the sources used to develop and
maintain the MPS at Ravenbrook Limited <http://www.ravenbrook.com/>. The
@@ -101,7 +143,7 @@
source release so far.
-4. DEVELOPING USING THE KIT
+5. DEVELOPING USING THE KIT
The MPS can be built on a wide variety of platforms. For Unix-like
platforms you will need the GNU Make tool. Some platforms (such as
@@ -182,13 +224,13 @@
class).
-5. TESTING
+6. TESTING
There is an extensive regression test suite in the "test" directory, but
we have not yet had time to make it easy to run.
-6. BUILDING A RELEASE
+7. BUILDING A RELEASE
The procedure for building a release of the MPS is in
"procedure/release-build". This will only be of interest if you are
@@ -197,7 +239,7 @@
to discuss it.
-7. CONTRIBUTING YOUR WORK
+8. CONTRIBUTING YOUR WORK
We'd like to include improvements to the MPS in the distributions from
Ravenbrook Limited. Please consider putting your work under a
@@ -208,7 +250,7 @@
accurate notes) and the procedures have been maintained.
-8. GETTING HELP
+9. GETTING HELP
You can obtain expert professional support for the MPS from Ravenbrook
Limited <http://www.ravenbrook.com/>, the developers of the MPS, who
@@ -221,7 +263,7 @@
general information.
-9. LICENSING
+10. LICENSING
The MPS is distributed under an open source license (see the file
"license.txt"). The license is designed to make it possible for you to
@@ -248,17 +290,22 @@
B. DOCUMENT HISTORY
-2002-05-20 RB Created based on template from P4DTI project.
-2002-06-18 NB Minor updates and corrections.
-2002-06-18 RB Removed obsolete requirement for MASM.
-2002-06-19 NB Added note on self-extracting archive
+2002-05-20 RB Original author: Richard Brooksby, Ravenbrook Limited.
+2002-05-20 RB Created based on template from P4DTI project.
+2002-06-18 NB Minor updates and corrections.
+2002-06-18 RB Removed obsolete requirement for MASM.
+2002-06-19 NB Added note on self-extracting archive
+2006-01-30 RHSK Update from "1.100.1" to "1.106.1".
+2006-03-30 RHSK Add section 2: What's new.
+2006-04-11 RHSK Update from "1.106.1" to "1.106.2".
+2006-04-14 RHSK Merge updates from version/1.106 back to master.
C. COPYRIGHT AND LICENSE
-Copyright (C) 2001-2002 Ravenbrook Limited <http://www.ravenbrook.com/>.
-All rights reserved. This is an open source license. Contact
-Ravenbrook for commercial licensing options.
+Copyright (C) 2001-2002, 2006 Ravenbrook Limited. All rights reserved.
+<http://www.ravenbrook.com/>. This is an open source license.
+Contact Ravenbrook for commercial licensing options.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
@@ -294,4 +341,4 @@
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-$Id: //info.ravenbrook.com/project/mps/master/readme.txt#3 $
+$Id: //info.ravenbrook.com/project/mps/master/readme.txt#5 $
More information about the chatter
mailing list