• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..25-Mar-2015-

libp2c/H24-Jun-2013-2,4181,859

AUTHORSH A D16-Apr-201228 21

BugsH A D16-Apr-2012193 64

COPYINGH A D16-Apr-201217.6 KiB341281

ChangeLogH A D16-Apr-20124.8 KiB181129

INSTALLH A D16-Apr-201215.2 KiB366284

Makefile.amH A D16-Apr-2012650 1412

NEWSH A D16-Apr-2012193 64

READMEH A D16-Apr-20125.7 KiB165112

README.060dH A D16-Apr-2012224 96

analyze.cH A D16-Apr-20127.4 KiB334285

analyze.hH A D16-Apr-2012565 3419

analyze.pasH A D16-Apr-20126.2 KiB182165

cfuncs.cH A D04-Oct-20121.9 KiB9276

cfuncs.hH A D16-Apr-20121.5 KiB7356

config.hH A D16-Apr-20122.5 KiB9127

config.h.inH A D16-Apr-20122.3 KiB9060

configure.acH A D16-Apr-2012798 3426

control.cH A D16-Apr-20125.3 KiB275171

control.hH A D16-Apr-20121.4 KiB5332

control.pasH A D16-Apr-20126.8 KiB199145

files.cH A D09-Jul-20128 KiB380312

files.hH A D16-Apr-2012759 3924

files.pasH A D16-Apr-20126.7 KiB197172

globals.cH A D09-Jul-20125.9 KiB349270

globals.hH A D16-Apr-20124.1 KiB155103

globals.pasH A D16-Apr-20127.5 KiB248209

lyrics.cH A D16-Apr-201219.2 KiB870718

lyrics.hH A D16-Apr-2012881 3824

lyrics.pasH A D16-Apr-201215.7 KiB456406

mtx.cH A D16-Apr-201210.8 KiB506416

mtx.hH A D16-Apr-2012566 3117

mtx.pasH A D16-Apr-20129.3 KiB281245

mtxline.cH A D16-Apr-201215.9 KiB845668

mtxline.hH A D16-Apr-20122.7 KiB8459

mtxline.pasH A D16-Apr-201215.1 KiB448383

multfile.cH A D04-Oct-20124.3 KiB236181

multfile.hH A D16-Apr-20123 KiB8828

multfile.pasH A D16-Apr-20126.5 KiB197127

notes.cH A D16-Apr-201211.8 KiB548420

notes.hH A D16-Apr-2012647 3520

notes.pasH A D16-Apr-20129.5 KiB281220

preamble.cH A D16-Apr-201224.5 KiB1,135954

preamble.hH A D16-Apr-2012854 4326

preamble.pasH A D16-Apr-201220.3 KiB625567

prepmx.cH A D16-Apr-201219.8 KiB888735

prepmx.pasH A D16-Apr-201215.4 KiB445376

status.cH A D16-Apr-201212.4 KiB650523

status.hH A D16-Apr-20121.5 KiB5838

status.pasH A D16-Apr-201211.8 KiB349299

strings.hH A D16-Apr-2012963 3521

uptext.cH A D16-Apr-20125.1 KiB278219

uptext.hH A D16-Apr-2012490 2614

uptext.pasH A D16-Apr-20123.5 KiB120105

utility.cH A D16-Apr-20127.2 KiB394305

utility.hH A D16-Apr-20121.2 KiB4225

utility.pasH A D16-Apr-20126.4 KiB195146

README

1                   M-Tx Preprocessor Source Code
2
3
4This is a development version of "prepmx", the M-Tx Preprocessor.
5It contains the file "mtx.tex" and all the sources for generating the
6binary executable file ("prepmx", "prepmx.exe", etc., depending on your
7operating system).  There is no documentation: find the latest available
8mtxD????.zip and read the Corrections file.  There are no examples: find
9the latest available mtxX????.zip.  Or stay with the most recent stable
10release for those.
11
12The development version is provided for those who need more recent features
13than the most recent stable release has, in the hope that they will be
14willing to report bugs and maybe even suggest how those can be fixed.
15Send e-mail to Dirk Laurie <dlaurie@na-net.ornl.gov>.
16
17You will have found this README in a file called something like mtxP054f.zip
18(which containes Pascal code) or mtxC054f.zip (which contains C code).
19I will refer to that file as mtxP????.zip or mtxC????.zip.
20
21You need one of the following compilers.  A later version than specified
22should also work, but an earlier one probably will not.
23  1. Free Pascal 1.0.10 (for mtxP????.zip)
24  2. Borland Pascal 7.0 (for mtxP????.zip)
25  3. Any ANSI-compliant C compiler (for mtxC????.zip)
26  4. The p2c package plus any ANSI-compliant C compiler (for mtxP????.zip)
27The first of these is recommended, since that is the compiler I use.
28I try to stay compatible with the other three, but this may not always
29be possible.
30
31"GNU System" means any system on which standard GNU utilities such as "bash"
32and "make" is available.  Typical GNU systems are (a) Linux (b) Windows with
33the Cygwin package installed (c) other systems on which an appropriate
34package has been installed.  You do not need a GNU system to use M-Tx,
35but it is easier to make the executable on a GNU system.
36
37Read Section 1 below, and, depending on which compiler you have,
38one of the other sections.  If you have no appropriate compiler,
39visit http://www.freepascal.org/ to see whether there is a Free Pascal
40compiler for your system (at present, MacOS is the only popular operating
41system not available); if not, get an ANSI compliant C compiler and read
42Section 6.
43
44
45   Contents
46
471. Text file format and unzipping
482. Compiling with Free Pascal
493. Compiling with Borland Pascal 7.0
504. Compiling with p2c
515. Compiling with a C compiler on a GNU system
526. Compiling with a C compiler on a non-GNU system
537. For experts only
54
55                   1. Text file format and unzipping
56
57Change to some empty directory and unzip the distribution file.  YOU MUST
58UNZIP THE FILES USING AN UNZIPPER THAT CAN CONVERT TEXT FILES TO YOUR
59SYSTEM'S FORMAT.  Some things may work even if you don't (maybe even
60everything, if your system happens to use the same text format as the
61system on which the zipfile was made) but then any later errors will
62only be more mysterious because of that.  It may be necessary to set
63special options in your unzipper to achieve this.  On a GNU system,
64the command is
65   unzip -a mtxP????.zip
66
67
68                   2. Compiling with Free Pascal
69
70Free Pascal is available from for most current operating systems, including
71Linux, SunOS and Windows.
72
73If your system has GNU Make, simply type
74
75  make
76
77Otherwise, type
78
79  fpc -B -So prepmx
80
81to make the executable.
82
83
84                   3. Compiling with Borland Pascal 7.0
85
86This compiler is a 16-bit compiler specific to MSDOS, even though it
87runs under Windows and under DOS emulators on other 32-bit systems.
88It cannot handle very large code and data segments, and unfortunately
89it is necessary to cripple M-Tx somewhat to make it fit in, as follows:
90
913.1 Edit the file "globals.pas" and change the lines
92
93          lines_in_paragraph = 100;
94	  max_words = 128;
95	  max_notes = 128;
96
97    to
98
99          lines_in_paragraph = 50;
100	  max_words = 64;
101	  max_notes = 64;
102
1033.2 Type
104
105        bpc -b prepmx
106
107    to make prepmx.exe.
108
109
110                   4. Compiling with p2c
111
112This route is only available if you have a GNU system with a C compiler
113and the package p2c (on old Red Hat systems, both p2c and p2c-devel).  Type
114
115  make prepmxc
116
117to make prepmx.  On this system only, you can make the mtxC????.zip file
118that corresponds to your mtxP????.zip file with
119
120  make Czip
121
122
123                   5. Compiling with a C compiler on a GNU system
124
125Just type
126
127  make prepmxc
128
129to make prepmx.
130
131
132                   6. Compiling with a C compiler on a non-GNU system
133
134Your C compiler must be ANSI compliant (sorry, Visual C++ 6.0 is not
135such, but Turbo C++ is).  Then issue a command that will compile and
136link all the .c files to produce an appropriately named executable.
137The command line will depend on your system; for example
138
139  cc *.c -o prepmx
140
141should work on non-GNU Un?x systems.
142
143
144                   7. For experts only
145
146You can modify the source code as you wish -- this is open source software
147and the copyright is GPL.  If you wish to redistribute your modified version,
148please augment the name so that there is no risk of confusion: e.g. if you
149are Johannes Brahms and you have made changes to mtxC054f.zip, call it
150mtxC054f-brahms.zip.
151
152Even better, send me an e-mail with your changes so that I can insert them
153into the current development version.
154
155The primary source is the Pascal version; the C version is made with p2c as
156described in Section 4.  Therefore, any change made to the C code is volatile;
157only changes made to the Pascal version become permanent.
158
159If you make both Pascal and C executables, it is your responsibilty to
160move or rename the first executable, otherwise it will be overwritten.
161Moreover, it is possible to confuse the Makefile, since object files
162from Pascal and C compilations may well have the same name; you will
163then get numerous error messages.  The safe thing is to "make clean"
164before switching languages.
165

README.060d

1M-Tx 0.60d is a test version of M-Tx 0.60. Please try it out and report any
2error observations to Christian Mondrup, reccmo@daimi.au.dk and
3Dirk Laurie, dpl@sun.ac.za
4
5Changes:
6========
7
8- Fixed a bug with non-labeled ties
9