May 19, 2006

ANN: PLT-Scheme 301.15

Posted in Scheme at 11:06 am by pmatos

And another major breakthrough, 301.15, thanks to the PLT Team!

MzScheme and MrEd are now version 301.15 in the SVN repository trunk.

This version is the next-to-last step in the overhaul that I described
for the 301.13 release:
http://list.cs.brown.edu/pipermail/plt-scheme/2006-April/012654.html

Changes:

* Documentation has moved from plt/collects/doc to plt/doc.

By tomorrow or so, when you update your documentation, the copies in
plt/collects/doc will be deleted, and the new copies will be
installed in plt/doc, instead. Also, if the current user cannot
write to the main “doc” directory, docs are installed instead to a
user-specific “doc” directory.

The old plt/notes directory is now plt/doc/release-notes.

* Under Unix, if you run `configure’ with a –prefix argument, then
the resulting install tree has a different shape than the in-place
tree:

collects -> ${prefix}/lib/plt/collects/…
[shared] libs -> ${prefix}/lib/…
.h files -> ${prefix}/include/plt/…
docs -> ${prefix}/share/plt/doc/…
extra C objects -> ${prefix}/lib/plt/…

You can get the old shape by using –enable-origtree.

If you run `configure’ with no –prefix argument, then (as before),
installation produces an in-place build.

In addition to –prefix, standard `configure’ arguments like
–bindir provide fine-grained control over the installed tree.

Installation generates a “config.ss” module in the “config”
collection, and this information is used by the “dirs.ss” library in
“setup” to communicate the installation tree to all PLT tools and
libraries.

* Moved plt/teachpack to a “teachpack” collection.

As always, let us know if you encounter any problems. It may take us a
couple of days to get the nightly bundles working properly.

The next and final step is to support truly “stand-alone” executables.
Currently, when you create an executable in DrScheme for Windows or Mac
OS X (or certain Unix configurations), the resulting binary is
hard-wired to your installation (e.g., to find the MzScheme DLLs). So,
the last step in our overhaul is to provide tools for assembling all
needed DLLs, etc., together in a package that can be run on any machine
(with the same OS).

Matthew

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: