Installation

Installing MCL 4.0

Aliases to the shared libraries "pmcl-kernel-4.0", "pmcl-library-4.0", and "pmcl-compiler-4.0" may be placed in your Extensions folder. This would allow your MCL-based applications to use them regardless of where the applications are located. Otherwise, these libraries or aliases to them must be in the same folder as the application when it is launched.

If you are working with the "Demo Version" of MCL 4.0, you need not worry about these shared libraries as they are built into the demo version.

Some of the files in the "Library" folder are referenced at runtime and/or compile-time by the MCL 4.0; by default, the "Library" folder is expected to be in the same folder as the MCL 4.0 application.

MCL 4.0 uses the Macintosh Thread Manager to support multiple processes. If your Macintosh does not have the Thread Manager installed, you should copy the file "ThreadsLib" from the MCL 4.0 distribution to your Extensions folder and reboot before running MCL 4.0.

IMPORTANT: Only install this version of the Thread Manager if your copy of the Macintosh OS does not already include it. System 7.5.3 includes the Thread Manager. To tell whether an older version of the Macintosh OS already has the Thread Manager installed, start up MCL 4.0 and select the Processes command from the Tools menu. If the dialog shows an "Initial" process but no "Listener" process, then your Macintosh does not have the Thread Manager installed. You should install it and reboot. Checking your Extensions folder for the presence of a "ThreadsLib" file is not a reliable way to check for the presence of the thread manager, as it may be included in the System file.

If you are upgrading from a previous version of MCL, you will need to recompile your fasl files.

Generated with Harlequin WebMaker