
                          Compiling Mup for UNIX

       1.  Compiling Mup for UNIX

       Mup has been compiled successfully on UNIX SV_R4 for x86,
       Linux, several versions of SUN OS, and other UNIX
       variations.  We cannot guarantee that it will work on your
       system, but it generally ports with no more than minimal
       changes.

       First, ftp the Mup documentation package in UNIX format
       (mup43doc.tar.gz) and unpack it.
          gunzip mup43doc.tar.gz
          tar xf mup43doc.tar

       Next, ftp the "mup43src.tar.gz" Mup source package file and
       unpack it:
          gunzip mup43src.tar.gz
          tar xf mup43src.tar

       This will create a "mup" directory.
          cd mup
       Compile Mup. Generally, something like the following will
       work:
          cc -o mup *.c -lm
       For most UNIX compilers, the "-o mup" will cause the program
       to be put into a file called "mup," and the "-lm" will cause
       the math library to be included (That's a lower-case letter
       "el" not a one).  You may also want to use other options.
       For example, for many compilers "-O" (that's a capital
       letter "oh" not a zero) will run the optimizer, and "-s"
       will strip the resulting program to save disk space.

       Copy mup into your $HOME/bin or a similar directory in your
       $PATH.
          cp mup $HOME/bin/mup

       If you already have a means of displaying PostScript files,
       such as pageview or ghostview, you can simply pipe the
       output of Mup into your display program.  Otherwise you can
       use Ghostscript, which is free. You can download Ghostscript
       from http://www.cs.wisc.edu/~ghost, or
       http://www.ghostscript.com/.  We've found that on some
       systems, Ghostscript compiles with lots of warnings, but it
       works okay anyway. You'll probably want to have around 15 MB
       of disk space available for source, object, and fonts.  If
       you're really short of disk space, the absolute minimum
       fonts that Mup needs are Times Roman, Times Italics, Times
       Bold, Times Bold-Italics, New Century Bold, Zapf Chancery
       Italics, and Zapf Dingbats (and you only need the Zapf fonts
       if you use pedstyle=pedstar).  If you use tablature staffs,
       Mup uses Helvetica Roman and Helvetica Bold for them.  On
       our UNIX SV_R4 x86 systems, using one version of
       Ghostscript, in order to get it to compile, we had to remove
       the "const" from the definition of op_def_ptr in opdef.h and
       remove the "const" from the definition of const_os_ptr in
       ostack.c.  Your experience may be different.

       Once you have installed Ghostscript, compile the mupdisp
       program for displaying Mup output on screen. See the comment
       at the top of mupdisp.c for suggestions on compiler options
       to try.

       Copy mupdisp into your $HOME/bin or similar directory.
          cp mupdisp $HOME/bin/mupdisp

       The mupdisp program works on the AT386 $TERM type under UNIX
       x86 or under X-windows. If you have a different display
       type, you may need to write your own display functions. In
       most cases, you'll only need to write 6 short functions, and
       you can use the examples in at386.c, dos.c, or xterm.c for a
       general template of the functions. You will also need to
       update dispttyp.h and init.c appropriately.

       If you want to supply your own fonts to override the
       standard Mup fonts, you can compile the mkmupfnt program:
          cd mkmupfnt cc -o mkmupfnt mkmupfnt.c

       A shell script called "mupprnt" is included for printing Mup
       files using Ghostscript.  Copy mupprnt to your $HOME/bin or
       other appropriate directory.
          cp mupprnt $HOME/bin/mupprnt
       You will need to set the GS_DEVICE shell variable to the
       proper value for your printer. If you don't know what to set
       it to, the comment at the top of mupprnt may help, or check
       your Ghostscript documentation.

       Once you have everything installed, you can remove the .tar
       files if you wish, to free up disk space.
          rm mup43doc.tar mup43src.tar

       2.  Getting Mup running for the first time

       Once you get Mup to compile successfully, try running it.
       The first time you run Mup, it should give you a message
       indicating Mup is shareware, and asking you to read the Mup
       license agreement. It will then tell you to create a
       particular file.  By creating this file, you agree to abide
       by the Mup license, and Mup will be turned on for normal
       operation.

       Try running Mup on the sample input files (sample.mup and
       star.mup ).  Verify that the output you get matches the
       corresponding sample output files (sample.ps and star.ps ).
       You will find differences in some of the numbers, comments,
       timestamp, filenames, etc, but otherwise, in general the
       PostScript output you get should be similar to the sample
       output files provided, and if you display them, the results
       should look pretty much identical.

       If Mup fails to run properly on the sample files, either
       your system has uncovered a bug that we haven't seen yet or
       your machine has some incompatibility. You can turn on
       debugging, by compiling with -DDEBUG and running with -dN,
       where N is a bitmap of debugging flags, to help pinpoint
       where bugs may be. The Mup User's Guide, which is included
       in the Mup documentation package, explains the bits of the
       debugging flags. If you get stuck, you may contact us at
       support@arkkra.com and we will try to help.

       If you need to make any changes in order to get Mup to
       compile and run successfully, please let us know.  If you
       find anything confusing, we'd like to know that too.  We
       want Mup to be as solid, portable, useful, and easy to use
       as possible.

       Also, please let us know if there are ways we can improve
       the Mup documentation package.

       If you receive messages beginning with "internal error" this
       usually indicates a program bug, so we'd like to know about
       them. An exception is when you get a message about being
       unable to allocate memory when there really isn't any memory
       left. If you get other internal errors, please send us a
       copy of an input file and any other information that may
       help us reproduce the problem, so we can try to fix it in
       the next Mup release.

       Mup is shareware. Once you get Mup up and running, you can
       try it out for free to decide whether you want to use it or
       not. If you like it, execute
          mup -r
       to get a copy of the shareware registration form.  The
       registration fee is $29.  See the license file for license
       details.

       Provide feedback (bugs reports, comments, suggestions,
       questions) to:  support@arkkra.com
