This chapter will explain where all the files coming with the archive should end up.


Because there is not much to do, there is no installer script. You will have to perform some simple steps the first time you install hsc. If the descriptions below are not sufficient for you to figure out what to do, you do not want to use this tool anyway.

Simple Installation

It's recommended to leave the whole hsc directory in one piece. Therefor extract the archive somewhere to your hard disk, for example to work:hsc.

You now have to add this directory to your workbench search path. This can be performed adding a line like the one you can find below to your user-startup
Path work:hsc ADD
After rebooting, you can open a shell and type in ``hsc help'', and hsc should come up with a short information message.

Minimum Installation

For a minimum installation, only hsc and hsc.prefs are required. If you want to utilize the project management capabilities of hsc, also hscdepp and hscpitt are needed.

Copy the binaries to somewhere in your workbench search path (for example, to c:) and hsc.prefs anywhere else and set HSCPATH according to this.

Making It Resident

All binaries should already have the the pure bit set. If not, you can do this by entering

protect hsc/hsc add p
protect hsc/hscdepp add p
protect hsc/hscpitt add p

in a shell.

To make the binaries resident on every startup, add the lines

resident hsc
resident hscdepp
resident hscpitt

to the user-startup.

Important: For resident programs, PROGDIR: is not defined. You will have to take care that hsc is able to find hsc.prefs before it tries to scan PROGDIR: for it. This can be done by by setting the environment variable HSCPATH or by placing hsc.prefs in the current directory for every project. Otherwise you will notice an annoying requester, which will ask you to ``insert volume PROGDIR: into any drive''.


For the RiscOS distribution, you can find a file called ReadMe in the directory riscos explaining these details.

NeXTStep, AmigaOS/ixemul, BeOS, Unixoid Systems

Maybe you will have to compile the sources yourself. Refer to the chapter about the Source Code for details.

For installation, the first few lines of this Makefile are interesting for you. They define two symbols you might want to change. INSTALL specifies the install program to be used. Normally the default should be fine.

An exception of this is when you want to compile for AmigaOS/ixemul. In this case you maybe want to set INSTALL=/bin/install or otherwise sys:c/install will be used, which does a completely different job - it makes a disk bootable.

The default for INSTDIR will attempt to to copy the binaries to /usr/bin/ and some other data to /usr/lib/. This will only work if you have write access to these directories.

If you are normal luser, you can modify this symbol to for instance
Make sure that you also have created $HOME/bin/ and $HOME/lib/ before starting the installation process. Or maybe you prefer
INSTDIR = /usr/local
because of philosophical reasons I never really understood. In any case, a
make install
should copy all files to the desired locations.