The main Mathematica distribution CD-ROM includes certain standard add-ons, which are installed in the AddOns subdirectory of the main Mathematica directory.
Add-ons that come with Mathematica.
Add-on applications that are not part of the Mathematica distribution are typically installed in the directory specified by the Mathematica global variable $AddOnsDirectory. Add-ons that are intended for one particular user are typically located in the user-specific directory specified by $UserAddOnsDirectory.
Typical values of $AddOnsDirectory.
Typical values of $UserAddOnsDirectory.
An add-on may be loaded when needed during a session, or it may be set up to load automatically when the Mathematica kernel starts up, depending on where it is placed.
Subdirectories under $AddOnsDirectory and $UserAddOnsDirectory.
With the default setting for the kernel $Path variable, an add-on can be loaded from within a Mathematica session simply by using the command <<name`. This will load the init.m file for the add-on, which should in turn be set up to load other necessary files or packages.
By placing an add-on under the Autoload subdirectory of $AddOnsDirectory or $UserAddOnsDirectory, you can have Mathematica automatically load the add-on whenever you start the kernel or the front end.
Typical possible contents of the directory for an add-on.
Note that with the default setting for the front end documentation path, all documentation in Documentation directories will automatically show up in the front end Help Browser.
MathLink development material.
Note that on some systems you may need to copy files from the DeveloperKit directory into the actual directories that you are using for software development.
Windows 95/NT 4.0 and Above
Shared libraries are used.
Example projects are provided for Microsoft Visual C/C++, Borland C/C++, Symantec C/C++, Watcom C/C++ and Metrowerks CodeWarrior C/C++ integrated development environments.
Fat shared libraries are used.
Example projects are provided for Metrowerks CodeWarrior, MPW and ThinkC integrated development environments.
Statically linked libraries are provided for all systems.
Dynamically linked libraries are provided whenever systems support them.
Makefiles are provided for the example programs.
THIS IS DOCUMENTATION FOR AN OBSOLETE PRODUCT.
SEE THE DOCUMENTATION CENTER
FOR THE LATEST INFORMATION.