Compiling Bluefish from source

From Bluefish Wiki
Revision as of 16:30, 4 January 2023 by DrMartinus (talk | contribs) (→‎Building (assumes required packages have been installed): corrected the path to autogen.sh)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Compiling bluefish from source tarballs[edit]

installing the requirements[edit]

Build requirements:

  • a C compiler (for example gcc or clang-gcc)
  • gnu make

Library / header file requirements:

  • gtk+ 2 or 3 development files (sometimes called libgtk2.0-dev or libgtk2-devel, or libgtk-3-dev)
  • libxml2 development files (sometimes called libxml2-dev or libxml2-devel)

Optional libraries / header files:

  • libenchant + development files (for spell checking, libenchant-dev)
  • libgucharmap + development files (for the character map side pane plugin, libgucharmap-dev)
  • python development files (python-dev or python-devel)

Debian and Ubuntu packages required[edit]

  • automake
  • autoconf
  • make
  • libtool
  • intltool
  • libgtk-3-dev
  • libxml2-dev

and optional

  • libenchant-dev
  • libgucharmap-2-90-dev
  • python-dev

Getting and compiling[edit]

  • get the latest source from http://www.bennewitz.com/bluefish/stable/source/
  • unpack
    • for a gzipped file tar -xzf bluefish-2.2.xxxx.tar.gz
    • for a bzipped file tar -xjf bluefish-2.2.xxxx.tar.bz2
  • cd bluefish-2.2.xxxx
  • run ./configure
  • run make
  • switch to root and run make install

Compiling bluefish straight from subversion[edit]

Building (assumes required packages have been installed)[edit]

svn checkout https://svn.code.sf.net/p/bluefish/code/trunk bluefish-code
cd bluefish-code/bluefish
./autogen.sh
./configure
make
sudo make install

Debian and Ubuntu packages required to build from subversion[edit]

  • libtool
  • intltool
  • automake
  • autoconf
  • make
  • libgtk-3-dev
  • libenchant-dev
  • libgucharmap-2-90-dev
  • libxml2-dev
  • subversion
  • python-dev