Chapter 2. Installing Bluefish

Table of Contents

1. Requirements
2. Quick Standard Installation
3. System Specific Installation Issues
4. Installing a Bluefish Source Distribution
4.1. Quick Installation Overview
4.2. Installing from Development Source Tree
4.3. Problems Compiling?
5. Configure Options
5.1. Standard configuration flags
5.2. Flags personal to bluefish
6. Installing a Binary Distribution
7. Post-installation Setup

1. Requirements

Bluefish aims to be portable, that is, wherever GTK is ported. A comparatively small set of external libraries are necessary for it to work. Any recent GNU/Linux distribution or other *NIX with GTK2 installed should be sufficient. In addition to the list of requirements below, you may also want to look at Section 3, “System Specific Installation Issues”. Note: These requirements fit the GTK2-version. If you only have GTK1, you want the last GTK1-version, v0.7.

The main requirements:

  • gtk v2.0
  • libpcre

Optional requirements:

  • gnome_vfs - for remote file support
  • libaspell - spell checker
  • grep & find - used by the advanced open dialog . Remember to add link to the advanced open description

Compiling Bluefish requires a few additional packages. (Remember that binary packages exists for many platforms. It is likely you won't need to compile ;-) ). Now, let's assume you want to compile, perhaps to get the latest and greatest from CVS. The requirements are as follows:

  • Development files (header files, etc) for the packages above. These are often distributed as separate packages. There is also a high probability you have these installed already.
  • gcc - Bluefish has been tested to compile on the 2.95 and 3.x branches.
  • gmake or BSD make
  • autoconf - only if you are going to compile from CVS