Debian systems require the following packages, along with their depencencies:

	mozilla-dev (>= 1.0)
	libnspr-dev (>= 1.0)
	automake
	libtool
	libgdk-pixbuf-gnome-dev
	gettext
	libgdome2-dev
	libglade-gnome-dev
	libpanel-applet-dev
	libpopt-dev
	libsigc++-dev
	libgconf-dev
	uuid-dev
		

Besides Mozilla and libnspr, all packages are available on the Woody distribution. Use apt-get install to install the above packages (for example, apt-get install gettext).

Step 2: Download the SashXB Runtime source

Get the source: sashxb-1.1-2.src.rpm | sashxb-1.1.tar.gz

There are also nightly builds/tarballs (including RPMs). These are for testing only. These are in no way guaranteed to work/compile. But they probably will. If a certain file (such as an RPM) is not there in the latest build, it is probably because the build broke for some reason. Try one of the earlier builds or wait until the build is fixed.

To checkout the source using CVS, set your CVSROOT environment variable:

> export CVSROOT=:pserver:anonymous@anoncvs.gnome.org:/cvs/gnome
         

or if you're using a cshell variant,

> setenv CVSROOT :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome
         

Then login and get the source:

> cvs login
> cvs -z3 checkout -P SashXB
> cvs -z3 checkout -P SashComponents
        

Build instructions are location in the README.make files in the top level directories.

Step 3: Compile and Install the SashXB Runtime

To compile SashXB, simply

> cd SashXB-1.1
> ./configure     ( ./autogen.sh if you obtained the source through CVS )
> make
> su
...
root> make install
         

autogen will fail if it detects any unmet dependencies.

If you have compiled mozilla from source or have an otherwise unusual mozilla install, you must specify the details (i.e. where the different mozilla directories are) when invoking autogen. Use a combination of --with-mozilla-dist=dir, --with-mozilla-include=dir, --with-mozilla-lib=dir, and --with-mozilla-idl=dir.

To compile a release build, as opposed to a debug build, pass --enable-build-settings=release to autogen. Release builds enable compiler optimization and strip the final binaries of debugging symbols, often decreasing file size by a factor of 10.

By default, make install will install SashXB globally. If you'd rather install it elsewhere, use the --prefix=dir flag when invoking autogen (and don't su root to make install).

If the installation is successful, you should be able to run sash-task-manager, sash-runtime, sash-install, sash-wdf-editor, and sash-registry-editor.

Step 4: Compile and Install Extensions, Locations, and Weblications

Now that the runtime is installed, you probably want to test some of our Sash components. Since each component may have its own dependencies (for instance, the Jabber and Vorbis extensions require some underlying libraries), the extensions and locations have their own configuration scripts. However, we provide several scripts to automate the installation process: install-all in the toplevel SashComponents/ directory, and install-[extensions|locations|weblications].pl in the subdirectories. Some of these scripts take optional parameters; try running them with --help for more information.

If you'd like to install a location or extension individually, just

> cd [ext_dir]
> ./autogen.sh
> make install
		 

Note that compiling the GTK extension can take an extremely long time, so be patient!

For a weblication, sash-install *.wdf in its directory will do the trick.