No License

Download apps, toolboxes, and other File Exchange content using Add-On Explorer in MATLAB.

» Watch video

4.0 | 1 rating Rate this file 6 Downloads (last 30 days) File Size: 2.61 KB File ID: #3726 Version: 1.0

Toolbox Installer 2.2


Rasmus Anthin (view profile)


15 Jul 2003 (Updated )

Routines for easily installing and uninstalling toolbox directories.

| Watch this File

File Information

This kit contains four files for assisting the toolbox author to make a userfriendly alternative to EDITPATH for his/her toolbox. The author uses MAKEINSTALL to create an info-file that will be located in the base/home-directory of a particular toolbox. Then by including the INSTALL and UNINSTALL programs in your toolbox the user simply writes INSTALL to install the directories you specified (you don't have to specify the base directory) to the matlab path, or removing them from the matlabpath by using UNINSTALL.

You can at any instant check the info-file by executing the CHECKINSTALL command.

Example of usage:
The author does something like this:

» cd(fullfile(matlabroot,'toolbox','digitalsim'))
» disp(pwd)
» makeinstall gates latches flipflops registers counters

The user does something like this:

» cd(fullfile(matlabroot,'toolbox','digitalsim'))
» install


This file inspired Eqsp: Recursive Zonal Sphere Partitioning Toolbox.

MATLAB release MATLAB 5.2 (R10)
Tags for This File   Please login to tag files.
Please login to add a comment or rating.
Comments and Ratings (4)
23 Feb 2005 Norbert Marwan

Why not simply use the <a href="">makeinstall tool</a>? It provides the author of the toolbox with a single install file, dynamically created from the toolbox. Makeinstall or the installer, resp., is only ONE script, containing everything you need.

Comment only
16 Jan 2005 Rasmus Anthin

I think you can solve it by simply creating a pathdef.m on your account (with editpath or pathtool) if it's not there, then use the "-" flag for the installer. See "help install".

Comment only
10 Jan 2005 Paul Leopardi

I need something similar, what I would call a package installer. This would be for users who do not have system privileges and want to install a package in their home directory, etc. Instead of changing pathdef.m, it would need to change startup.m, or create it if it does not exist.

15 Aug 2003 Rasmus Anthin

I should point out that these routines use matlab's PATH2RC in order to write to the pathdef.m file.

Comment only
17 Jul 2003

I thought that ADDPATH would automatically update the pathdef.m file, which it doesn't. So this new version saves the path using PATH2RC.
Selection of pathdef.m to save to is now also possible.

Contact us