author wenzelm
Fri Mar 07 11:46:26 2014 +0100 (2014-03-07)
changeset 55974 c835a9379026
parent 55438 3b95e70c5cb3
child 58780 1f8c0da85664
permissions -rw-r--r--
more official const syntax: avoid educated guessing by Syntax_Phases.decode_term;
     1 Some notes on multi-platform support of Isabelle
     2 ================================================
     4 Preamble
     5 --------
     7 The general programming model is that of a stylized ML + Scala + POSIX
     8 environment, with as little system-specific code in user-space tools
     9 as possible.
    11 The basic Isabelle system infrastructure provides some facilities to
    12 make this work, e.g. see the ML and Scala modules File and Path, or
    13 functions like Isabelle_System.bash.  The settings environment also
    14 provides some means for portability, e.g. the bash function "jvmpath"
    15 to keep the impression that Java on Windows/Cygwin adheres to
    16 Isabelle/POSIX standards, although inside the JVM itself there are
    17 many Windows-specific things.
    19 When producing add-on tools, it is important to stay within this clean
    20 room of Isabelle, and refrain from overly ambitious system hacking.
    21 The existing Isabelle scripts follow a peculiar style that reflects
    22 long years of experience in getting system plumbing right.
    25 Supported platforms
    26 -------------------
    28 The following hardware and operating system platforms are officially
    29 supported by the Isabelle distribution (and bundled tools), with the
    30 following reference versions (which have been selected to be neither
    31 too old nor too new):
    33   x86-linux         Ubuntu 10.04 LTS
    34   x86_64-linux      Ubuntu 10.04 LTS
    36   x86_64-darwin     Mac OS X Lion (macbroy6)
    37                     Mac OS X Mountain Lion (macbroy30)
    38                     Mac OS X Mavericks (macbroy2)
    40   x86-cygwin        Cygwin 1.7 (vmbroy9)
    42 All of the above platforms are 100% supported by Isabelle -- end-users
    43 should not have to care about the differences (at least in theory).
    45 Fringe platforms like BSD or Solaris are unsupported.
    48 32 bit vs. 64 bit platforms
    49 ---------------------------
    51 Most users have 64 bit hardware and are running a 64 bit operating
    52 system by default.  For Linux this usually means missing 32 bit shared
    53 libraries, so native x86_64-linux needs to be used by default, despite
    54 its doubled space requirements for Poly/ML heaps.  For Mac OS X, the
    55 x86-darwin personality usually works seamlessly for C/C++ programs,
    56 but the Java 7 platform is only available for x86_64-darwin.
    58 Add-on executables are expected to work without manual user
    59 configuration.  Each component settings script needs to determine the
    60 platform details appropriately.
    62 The Isabelle settings environment provides the following variables to
    63 help configuring platform-dependent tools:
    65   ISABELLE_PLATFORM64  (potentially empty)
    69 The ISABELLE_PLATFORM setting variable refers to the 32 bit version of
    70 the platform, even on 64 bit hardware.  Using regular bash notation,
    71 tools may express their preference for 64 bit with a fall-back for 32
    72 bit as follows:
    76 Moreover note that ML and JVM usually have a different idea of the
    77 platform, depending on the respective binaries that are actually run.
    78 Poly/ML 5.5.x performs best in 32 bit mode, even for large
    79 applications, thanks to its sophisticated heap management.  The JVM
    80 usually works better in 64 bit mode, which allows its heap to grow
    81 beyond 2 GB.
    83 The traditional "uname" Unix tool usually only tells about its own
    84 executable format, not the underlying platform!
    87 Dependable system tools
    88 -----------------------
    90 The following portable system tools can be taken for granted:
    92 * GNU bash as uniform shell on all platforms.  The POSIX "standard"
    93   shell /bin/sh is *not* appropriate, because there are too many
    94   non-standard implementations of it.
    96 * Perl as largely portable system programming language.  In some
    97   situations Python may serve as an alternative, but it usually
    98   performs not as well in addressing various delicate details of
    99   operating system concepts (processes, signals, sockets etc.).
   101 * Scala with Java 1.7.  Isabelle/Scala irons out many oddities and
   102   portability issues of the Java platform.
   105 Known problems
   106 --------------
   108 * Mac OS X: If MacPorts is installed there is some danger that
   109   accidental references to its shared libraries are created
   110   (e.g. libgmp).  Use otool -L to check if compiled binaries also work
   111   without MacPorts.
   113 * Mac OS X: If MacPorts is installed and its version of Perl takes
   114   precedence over /usr/bin/perl in the PATH, then the end-user needs
   115   to take care of installing extra modules, e.g. for HTTP support.
   116   Such add-ons are usually included in Apple's /usr/bin/perl by
   117   default.
   119 * The Java runtime has its own idea about the underlying platform,
   120   which affects Java native libraries in particular.  In
   121   Isabelle/Scala the function isabelle.Platform.jvm_platform
   122   identifies the JVM platform.  Since a particular Java version is
   123   always bundled with Isabelle, the resulting settings also provide
   124   some clues about its platform, without running it.
   126 * Common Unix tools like /bin/sh, /bin/kill, sed, ulimit are
   127   notoriously non-portable an should be avoided.