Bluefish Wiki - User contributions [en]

Setting up a Windows Build Environment

2025-10-08T20:26:50Z

OlivierSessink: /* new documentation as of 2025, using MSYS2 for windows 10 or later */

= new documentation as of 2025, using MSYS2 for windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
pacman -S mingw-w64-ucrt-x86_64-python-pip
pacman -S mingw-w64-ucrt-x86_64-hunspell-en
</pre>
Install nsis 3.1 from https://sourceforge.net/projects/nsis/files/NSIS%203/3.01/

Now download the latest source tarball from the bluefish download server (b.t.w. right now, March 9 2025 there is no good tarball yet, the latest release in svn has many windows specific fixes), extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.:/c/Program\ Files\ $x86$/NSIS/
export lt_cv_deplibs_check_method='pass_all'
export MAKE="make -j4"
make -j4 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in a working executable in c:\bluefish\win32\build\ (the dir is win32 but it actually is a 64bit executable)
It still has some quirks, but that is improving.

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== OLD Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== OLD Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== OLD Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== OLD Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== OLD Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== OLD The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== OLD Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== OLD Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== OLD Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== OLD Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== OLD Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== OLD Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== OLD Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

== OLD Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-10-07T20:40:35Z

OlivierSessink: /* new documentation as of 2025, using MSYS2 for windows 10 or later */

= new documentation as of 2025, using MSYS2 for windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
pacman -S mingw-w64-ucrt-x86_64-python-pip
pacman -S mingw-w64-ucrt-x86_64-hunspell-en
</pre>
Install nsis 3.1 from https://sourceforge.net/projects/nsis/files/NSIS%203/3.01/

Now download the latest source tarball from the bluefish download server (b.t.w. right now, March 9 2025 there is no good tarball yet, the latest release in svn has many windows specific fixes), extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.:/c/Program\ Files\ $x86$/NSIS/
export lt_cv_deplibs_check_method='pass_all'
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in a working executable in c:\bluefish\win32\build\ (the dir is win32 but it actually is a 64bit executable)
It still has some quirks, but that is improving.

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== OLD Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== OLD Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== OLD Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== OLD Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== OLD Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== OLD The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== OLD Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== OLD Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== OLD Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== OLD Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== OLD Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== OLD Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== OLD Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

== OLD Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

How To Translate

2025-08-20T18:15:36Z

OlivierSessink:

== Translations ==

=== 1. Introduction ===
Bluefish has been translated into many different languages.

Translation process is not a difficult task but you will need some time because there are more than one thousand strings to be translated. <br />
There are seven translation directories in Bluefish development branch, one for main program and one for each plugin:
* po/
* src/plugin_about/po/
* src/plugin_charmap/po/
* src/plugin_entities/po/
* src/plugin_htmlbar/po/
* src/plugin_infbrowser/po/
* src/plugin_snippets/po/
* src/plugin_zencoding/po/
The good news are you don't need to be a programmer to make Bluefish speak your language and the only tool you need is a text editor (bluefish for example) or Poedit or the gnome translation editor. Bluefish uses po (Portable Object) files. A po file is just a plain text file that you can edit with your favorite text editor.

=== 2. PO files basics ===
In a typical po file there are five major types of entries:

# Those which begin with "#:" showing the places in the source code that contains the string being translated (there may be one or more) as: '<nowiki>#: ../src/about.c:123</nowiki>'
# Those which begin with "#," containing some flags (not always present) as: '<nowiki>#, c-format</nowiki>'
# Those which begin with "msgid" containing the English string being translated (it may be spanned in several lines) as: 'msgid "Authentication is required for %s."'
# Those which begin with "msgstr" containing the translated string as: 'msgstr "Une autorisation est requise pour accéder à %s."'
# Those which begin with "#~ " containing obsolete strings as: '<nowiki>#~ msgid "Save document as"</nowiki>'

[[Image:Man1_warning.png]] When an entry is tagged as fuzzy (i.e. when the line begins with "<nowiki>#, fuzzy</nowiki>"), that means it is probably incorrect.

[[Image:Man1_warning.png]] You have to make sure the translation is correct and then delete either the "<nowiki>#, fuzzy</nowiki>" line if this is the only flag on the line, or the ", fuzzy" part of the line if there are some other flags on the same line, like in "<nowiki>#, fuzzy, c-format</nowiki>".

[[Image:Man1_warning.png]] Remember that as long as a translation is marked "fuzzy", it will NOT actually be used!

[[Image:Man1_warning.png]] As far as obsolete strings are concerned, it is up to you to decide if you want to remove them. On one hand they can be reused in a latter version of the po file, on the other hand they make the po file bigger.

Hence, your task as a translator is to:

# Translate all empty msgstr entries
# Check all fuzzy entries, correct them if they are wrong and remove all fuzzy tags
# Optionally, remove obsolete strings
# Check that the po file ends with a blank line

=== 3. Shortcut keys ===
Shortcut keys, known as hotkeys or even accelerator keys, are defined as follows (look at the underscore, please):

<nowiki># src/toolbars.c:482</nowiki>
<nowiki>#: ../src/filebrowser.c:1453</nowiki>
msgid "/_Refresh"
msgstr "/_Actualizar"

It means that in the English locale the user have to press '''Alt'''+'''R''' to activate this particular GUI element. On the other hand if your locale is Spanish your shortcut key will be '''Alt'''+'''A'''.

[[Image:Man1_warning.png]] You have to keep in mind that two GUI elements must not have the same shortcut key at the same level.

= get the files =

== Normal access ==

retrieve the files from https://www.bennewitz.com/bluefish/devel/translations/ and send them by email to olivier (at) bluefish.openoffice.nl when you are finished.

== If you have developer access: working from subversion ==

==== Retriving last Bluefish version====
* 1. In your working space directory (eg ~/tranlations) run: <br />
svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/
that create the Bluefish SVN directory
* 2. '''cd bluefish/''' and for first installation run '''./autogen.sh'''
* 3. run '''./configure''' and '''make'''
* 4. you can now update all files.
see also [[Sending_Patches#Notes_for_translators]]
==== Sending your translation ====
see also [[Sending_Patches#Special_notes_for_translators]]
* 1. update your SVN copy. In Bluefish/ dirctory run:
svn update
* 2. The following step is not necessary but it will help you finding issues, which must be fixed, before your changes can be committed to the subversion tree. It requires an installation of the gettext tools. Please change `your_lang` with your language code ;)
find . -name your_lang.po | xargs msgcat --use-first -o - | msgfmt -o /dev/null --statistics -
* 3. create the tarball:
find . -name your_lang.po | xargs tar -cjf your_lang.tar.bz2
* 4. send the tarball

Setting up a Windows Build Environment

2025-03-12T20:42:33Z

OlivierSessink: /* new documentation as of 2025, using MSYS2 for windows 10 or later */

= new documentation as of 2025, using MSYS2 for windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
pacman -S mingw-w64-ucrt-x86_64-python-pip
</pre>
Install nsis 3.1 from https://sourceforge.net/projects/nsis/files/NSIS%203/3.01/

Now download the latest source tarball from the bluefish download server (b.t.w. right now, March 9 2025 there is no good tarball yet, the latest release in svn has many windows specific fixes), extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.:/c/Program\ Files\ $x86$/NSIS/
export lt_cv_deplibs_check_method='pass_all'
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in a working executable in c:\bluefish\win32\build\ (the dir is win32 but it actually is a 64bit executable)
It still has some quirks, but that is improving.

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== OLD Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== OLD Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== OLD Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== OLD Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== OLD Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== OLD The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== OLD Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== OLD Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== OLD Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== OLD Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== OLD Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== OLD Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== OLD Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

== OLD Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-12T20:41:55Z

OlivierSessink: /* new documentation as of 2025, using MSYS2 for windows 10 or later */

= new documentation as of 2025, using MSYS2 for windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
pacman -S mingw-w64-ucrt-x86_64-python-pip
</pre>
Install nsis

Now download the latest source tarball from the bluefish download server (b.t.w. right now, March 9 2025 there is no good tarball yet, the latest release in svn has many windows specific fixes), extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.:/c/Program\ Files\ $x86$/NSIS/
export lt_cv_deplibs_check_method='pass_all'
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in a working executable in c:\bluefish\win32\build\ (the dir is win32 but it actually is a 64bit executable)
It still has some quirks, but that is improving.

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== OLD Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== OLD Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== OLD Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== OLD Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== OLD Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== OLD The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== OLD Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== OLD Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== OLD Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== OLD Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== OLD Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== OLD Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== OLD Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

== OLD Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-09T19:33:39Z

OlivierSessink:

= new documentation as of 2025, using MSYS2 for windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>
Install nsis

Now download the latest source tarball from the bluefish download server (b.t.w. right now, March 9 2025 there is no good tarball yet, the latest release in svn has many windows specific fixes), extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.:/c/Program\ Files\ $x86$/NSIS/
export lt_cv_deplibs_check_method='pass_all'
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in a working executable in c:\bluefish\win32\build\ (the dir is win32 but it actually is a 64bit executable)
It still has some quirks, but that is improving.

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== OLD Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== OLD Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== OLD Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== OLD Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== OLD Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== OLD The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== OLD Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== OLD Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== OLD Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== OLD Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== OLD Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== OLD Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== OLD Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

== OLD Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-09T19:28:44Z

OlivierSessink:

= new documentation as of 2025, using MSYS2 for windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>
Install nsis

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.:/c/Program\ Files\ $x86$/NSIS/
export lt_cv_deplibs_check_method='pass_all'
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in a working executable but it still has some quirks

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== OLD Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== OLD Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== OLD Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== OLD Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== OLD Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== OLD The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== OLD Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== OLD Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== OLD Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== OLD Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== OLD Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== OLD Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== OLD Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

== OLD Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-09T08:29:55Z

OlivierSessink:

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>
Install nsis

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.:/c/Program\ Files\ $x86$/NSIS/
export lt_cv_deplibs_check_method='pass_all'
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in an executable but it doesn't start..

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-09T08:26:52Z

OlivierSessink:

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.
export lt_cv_deplibs_check_method='pass_all'
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in an executable but it doesn't start..

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-08T20:48:05Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.
export lt_cv_deplibs_check_method=${lt_cv_deplibs_check_method='pass_all'}
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
you might need to install some files that are missing:
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
the windows version cannot handle non-numeric versions, so remove any 'beta' or something like that from configure.ac
./autogen.sh
</pre>

This results in an executable but it doesn't start..

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-08T19:28:34Z

OlivierSessink:

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.
export lt_cv_deplibs_check_method=${lt_cv_deplibs_check_method='pass_all'}
make -j6 -f Makefile.mingw
</pre>

if you compile from svn
<pre>
cp remove-potcdate.sin /ucrt64/share/gettext/po/
cp insert-header.sin /ucrt64/share/gettext/po/
change the line AM_GNU_GETTEXT_VERSION([0.24]) in configure.ac to the installed gettext version
install the files
./autogen.sh
</pre>

This results in an executable but it doesn't start..

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-08T19:15:35Z

OlivierSessink:

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
PATH=$PATH:.
export lt_cv_deplibs_check_method=${lt_cv_deplibs_check_method='pass_all'}
make -j6 -f Makefile.mingw
</pre>

This results in an executable but it doesn't start..

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-01T15:13:44Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
./configure
make -j6
</pre>

This results in an executable but it doesn't start..

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/

= Old documentation =

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-03-01T15:13:18Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
./configure
make -j6
</pre>

This results in an executable but it doesn't start..

Resources I'm currently looking at:
* https://www.gtk.org/docs/installations/windows/#using-gtk-from-msys2-packages
* https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/
*

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T17:12:04Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

Now download the latest source tarball from the bluefish download server, extract it in C:/bluefish/ and run:
<pre>
cd /c/bluefish
./configure
make -j6
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T17:09:47Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-ucrt-x86_64-enchant
pacman -S mingw-w64-ucrt-x86_64-libxml2
pacman -S mingw-w64-ucrt-x86_64-autotools
pacman -S mingw-w64-ucrt-x86_64-libtool
pacman -S mingw-w64-ucrt-x86_64-cc
pacman -S mingw-w64-ucrt-x86_64-gtk3
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T17:01:22Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S gcc mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2 mingw-w64-ucrt-x86_64-autotools mingw-w64-ucrt-x86_64-libtool mingw-w64-ucrt-x86_64-cc
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T16:58:10Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S gcc mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2 mingw-w64-ucrt-x86_64-autotools mingw-w64-ucrt-x86_64-libtool
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T16:39:45Z

OlivierSessink: /* new documentation as of 2025, requires windows 10 or later */

= new documentation as of 2025, requires windows 10 or later =

Set windows into developer mode https://learn.microsoft.com/en-us/windows/apps/get-started/enable-your-device-for-development

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2 mingw-w64-ucrt-x86_64-autotools mingw-w64-ucrt-x86_64-libtool
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T16:33:44Z

OlivierSessink: /* new documentation as of 2025 */

= new documentation as of 2025, requires windows 10 or later =

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64. Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2 mingw-w64-ucrt-x86_64-autotools mingw-w64-ucrt-x86_64-libtool
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T16:31:29Z

OlivierSessink: /* new documentation as of 2025 */

= new documentation as of 2025 =

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Now start msys2-ucrt64

Install all requirements (like gtk3) with
<pre>
pacman -S mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2 mingw-w64-ucrt-x86_64-autotools mingw-w64-ucrt-x86_64-libtool
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T16:09:30Z

OlivierSessink: /* new documentation as of 2025 */

= new documentation as of 2025 =

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Install gtk3 with
<pre>
pacman -S mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2 mingw-w64-ucrt-x86_64-autotools mingw-w64-ucrt-x86_64-libtool
</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T16:05:35Z

OlivierSessink:

= new documentation as of 2025 =

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Install gtk3 with
<pre>
pacman -S mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2 mingw-w64-ucrt-x86_64-autotools

</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Setting up a Windows Build Environment

2025-02-28T15:59:56Z

OlivierSessink:

= new documentation as of 2025 =

Install msys2 according to https://www.msys2.org/wiki/MSYS2-installation/

Install gtk3 with
<pre>
pacman -S mingw-w64-x86_64-gtk3 mingw-w64-ucrt-x86_64-enchant mingw-w64-ucrt-x86_64-libxml2

</pre>

== Windows Build Status ==

Binary and plugins are running and should be fully functional. If you encounter unexpected behaviour or bugs, please report your problem to [https://bugzilla.gnome.org/enter_bug.cgi?product=bluefish our BTS].

=== Current Known Issues ===

* Socket code doesn't work so files can't be opened externally in a currently running copy of bluefish.
* Launching of external programs doesn't work.
* Editing of UTF files with a BOM headers is not currently supported.

=== Recent Build Environment Changes ===

If you are maintaining a build environment for Bluefish please check this subsection occasionally for important changes!

;2011-02-07
:The MingW project has created a new installer, which makes things much easier but also changes the way to create the build environment.

;2009-12-10
:If you build your own installers we now use a unicode version of NSIS, [http://www.scratchpaper.com/home Unicode NSIS], to support UTF-8 encoded translations.

;2009-09-23:
:The GNOME packages have been updated to reflect those versions which are included with Pidgin's GTK+ installer. This is currently being used as our target runtime environment for the Installer version of Bluefish. If you're first setting up your build environment you can skip this section as the information provided below is always up to date. If you already have a build environment setup you will need to update a few packages to the versions provided below. These include atk (1.26.0->1.24.0), glib (2.20.4->2.18.4), gtk+ (2.16.5->2.14.7), and pango (1.24.5->1.22.4).

:If you don't intend to run your builds of Bluefish outside of your MSYS environment this change is not required. However if you do wish to do so and wish to remain with GTK+ 2.16 you can use the [http://gtk-win.sourceforge.net/ GTK-Win] installer. This version is not officially supported by the windows development team as of yet because while it's fine for Bluefish it does break some features in Pidgin so keep this in mind if you use both programs.

== Setting up your Build Environment ==

The first step is of course to install and setup the MingW and MSYS environments. Start with the [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20101030/mingw-get-inst-20101030.exe/download automated MinGW installer]. When you are asked for the installation location you have to choose a path without spaces like <tt>C:\MinGW</tt> (but not necessarily this one). From the optional components choose at least the C++ compiler and the MSYS base system.

If you know what you are doing, you might alternatively download and unpack (unzip/untar/...) the packages manually or via the <tt>mingw-get</tt> tool.

=== Updating the Build Environment ===

In a second step all further necessary software needs to be updated and/or installed. You can download and extract them manually or via the <tt>mingw-get</tt> tool. To unzip things we need at least the <tt>unzip</tt> too:

<pre>mingw-get update
mingw-get install msys-unzip msys-wget</pre>

All MinGW and MSYS packages can be retrieved and installed using this way as long as some internet connection is available.

We further need some software by third parties (GNOME packages and it's dependencies). Extract them to the location, where MSYS has been installed. This place is usually <tt>C:\MinGW\msys\1.0\</tt>. Keep in mind, that this place is equal to the root directory <tt>/</tt> and to <tt>/usr/</tt> (as both are the same) in MSYS. And also <tt>/local</tt> and <tt>/usr/local</tt> are equal too. ''We install all third party software into <tt>/usr/local</tt>!'':

;''GNOME Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip gtk+-bundle_2.14.7-20090119_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat_2.0.1-1_win32.zip expat_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/expat-dev_2.0.1-1_win32.zip expat-dev_2.0.1-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool_0.40.4-1_win32.zip intltool_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/intltool/0.40/intltool-dev_0.40.4-1_win32.zip intltool-dev_0.40.4-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-2.5.zip libgnurx-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libgnurx-dev-2.5.zip libgnurx-dev-2.5.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2_2.7.7-1_win32.zip libxml2_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip libxml2-dev_2.7.7-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf_2.22.0-3_win32.zip GConf_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/GConf/2.22/GConf-dev_2.22.0-3_win32.zip GConf-dev_2.22.0-3_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2_2.14.16-1_win32.zip ORBit2_2.14.16-1_win32.zip]
:[http://ftp.gnome.org/pub/gnome/binaries/win32/ORBit2/2.14/ORBit2-dev_2.14.16-1_win32.zip ORBit2-dev_2.14.16-1_win32.zip]


;''External Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)
:[http://sourceforge.net/projects/win32svn/files/1.6.15/svn-win32-1.6.15.zip/download svn-win32-1.6.15.zip]

=== The Perl Issue ===

The last thing you need is Perl. The MSYS version is 5.6.1 which is not new enough to pass the configure script for a lot of programs including Bluefish. I use the MSYS 5.6.1 version for autoconf/automake/autogen.sh and an external version such as [http://www.activestate.com/activeperl/ ActiveState's] for anything that needs a newer version. Install the ActivePerl Perl version. Then edit <tt>/etc/fstab</tt> in your MSYS enviroment (usually <tt></tt>) and add the following line:

<pre>c:/programs/perl /opt/perl</pre>

so Perl is mounted to the MSYS environment.

== Configuring your Build Environment ==

You might set a few environment variables as follows.

<pre>PATH="/bin:/local/bin:/opt/perl/bin"
C_INCLUDE_PATH="/include:/local/include"
LIBRARY_PATH="/lib:/local/lib"</pre>

;Alternatively pass [http://bluefish.svn.sf.net/viewvc/bluefish/trunk/bluefish/config.site/config.msys our config.site script] for MSYS to configure to adjust PATH/CFLAGS/LDFLAGS easily.

Further we need to adjust the macro search path for aclocal:

<pre>echo /local/share/aclocal > /mingw/share/aclocal/dirlist</pre>

Because of a linker bug in the <tt>gconftool-2</tt> binary add this symbolic link:

<pre>ln -s /local/bin/libxml2-2.dll /local/bin/libxml2.dll</pre>

== Building External Packages ==

To build bluefish we need some libraries not available from the MinGW/MSYS project.

=== Installing Pre-Compiled Packages ===

Shawn Novak provides pre-compiled tarballs, which you just need to extract to <tt>/local</tt>:

;''Custom Packages'' install into MSYS local directory "<tt>/local</tt>" (<tt>C:\MinGW\local\</tt> or <tt>C:\Programs\msys\1.0\local\</tt>)

:[http://www.muleslow.net/files/mingw/aspell-0.60.6-bin-MinGW-20090901.tbz2 aspell-0.60.6-bin-MinGW-20090901.tbz2]
:[http://www.muleslow.net/files/mingw/enchant-1.5.0-bin-MinGW-20090901.tbz2 enchant-1.5.0-bin-MinGW-20090901.tbz2]

A full set of dictionaries for Aspell 0.60.6 can be found here: [http://www.muleslow.net/files/aspell/lang/ http://www.muleslow.net/files/aspell/lang/]

=== Building and Installing from the Source ===

If you wish to build your own version of these custom packages, these are the configure parameters used for the ones provided.
<ref>Note by Daniel Leidert: I further pass a short <tt>msys.site</tt> script with the following content to <tt>configure</tt>:

<pre>#!/bin/sh
PATH="/opt/perl/bin:$PATH"
prefix=/local
exec_prefix='${prefix}'
enable_shared=yes
enable_static=no
enable_maintainer_mode=yes
LDFLAGS="-L/local/lib -L/lib"
CFLAGS="-g -Wall -O2 -I/local/include -I/include -mwindows"
CPPFLAGS="-g -Wall -O2 -I/local/include -I/include"</pre>

The configure script is then called as follows together with the switches as shown above:

<pre>./configure CONFIG_SITE=msys.site ...configure options see above...</pre>
</ref>

;[ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.tar.gz Aspell 0.60.6]

In the aspell source add

#include "asc_ctype.hpp"

to the includes at '''common/file_util.cpp'''.

./configure --prefix=/local --disable-rpath --enable-win32-relocatable

;[http://www.abisource.com/downloads/enchant/1.6.0/enchant-1.6.0.tar.gz Enchant 1.6.0]

./configure --prefix=/local --enable-aspell --disable-ispell --disable-myspell


;[http://ftp.gnome.org/pub/GNOME/sources/gucharmap/2.32/gucharmap-2.32.1.tar.bz2 gucharmap 2.32]

Unfortunately gucharmap does not build out-of-the-box. The following instructions were taken from the [http://article.gmane.org/gmane.comp.web.bluefish.devel/2197 mailing list]. First apply the following patch by Daniel Leidert [http://www.muleslow.net/files/mingw/patches/gucharmap26.diff gucharmap26.diff] and then configure with the following commands.

patch -p0 <gucharmap26.diff
intltoolize -f
libtoolize -f
aclocal -I m4/ --force
autoheader -f
automake -f
autoconf -f
./configure --disable-gconf --disable-schemas-install --disable-scrollkeeper

== Building Bluefish ==

Check out the latest code from trunk:

<pre>svn checkout https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish</pre>

Run <tt>autogen.sh</tt> (uses perl 5.6.1). Then run <tt>configure</tt> (make sure, Perl from <tt>/opt/perl/bin</tt> is used; e.g. adjust PATH) and make:

<pre>./autogen.sh
./configure CONFIG_SITE=config.site/config.msys
make
make install</pre>

== Debugging Bluefish ==

For console debugging output, configure bluefish by passing '--enable-debugging-output' to <tt>./configure</tt>. Further CFLAGS should contain '-g' (default, also explicitly set by <tt>config.msys</tt>).

For debugging crashes install the [https://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Current%20Release_%20gdb-5.2.1/gdb-5.2.1-1.exe/download GNU Debugger (GDB)].

== Create the Installer ==
To compile the installer you'll need to have [http://www.scratchpaper.com/home Unicode NSIS] with the [http://nsis.sourceforge.net/UnTGZ_plug-in UnTGZ] plugin installed. You should also have makensis.exe in your path (such as in /opt/nsis).

To build the installer configure and build Bluefish with the following commands.

<pre>
./configure CONFIG_SITE=win32/config.nsis
cd win32
make -f Makefile.mingw installer
</pre>

==Notes and references==
References: <references/>

==See also==
[[Installing_Bluefish#Installing_Bluefish_on_Windows_XP.2FVista.2F7_.2832_bit.29|Existing win32 builds]]

Translations

2024-09-13T15:07:43Z

OlivierSessink: /* Current development translation status */

== Translations ==

Please send a message to the developer's list if you have questions, suggestions or would like to help with translations. By all means, don't wait for someone to give you the OK to start translating. Here are some instructions on [[How To Translate]].

== Current translation teams ==

It is good if there are multiple people for every language, so if anybody is on holidays or something and we want to do a Bluefish release we can have all languages updated, so please work in teams.

=== Active translators / teams ===
These translations are kept up to date (last updated Feb 13 2014):

Basque (EU) dooteo (at) euskalgnu org / Language-Team: itzulpena (at) euskalgnu org
Brazilian Portuguese (PT_BR) esfingemetal (at) gmail com
Catalan (CA) monica (at) probeta.net
Chinese (ZH_CN) mzf9527 (at) gmail com
Czech (CS) marek (at) manet cz / Language-Team: gnome-cs-list (at) gnome org
Danish (DA) fc (at) stilheden net / Language Team: dansk (at) dansk-gruppen dk
Dutch (NL) olivier (at) bluefish openoffice nl
Farsi (FA) Paymon Menhadji
French (FR) falsetti (at) clansco org
Galician (GL) correo.xmgz (at) gmail com
German (DE) Ralf.Kestler (at) gmx net, linux (at) drmartinus de
Hungarian (HU) urbalazs (at) gmail com / Language-Team: hu (at) li org
Italian (IT) bellingeri (at) netguru it
Japanese (JA) hmatrjp (at) users sourceforge jp
Norwegian (NB) chris (at) tellefsen net
Nynorsk (NN) l10n (at) landro net
Polish (PL) dawajpoczte (at) gmail com
Russian (RU) george (at) altlinux org / Language-Team: gnome-cyr (at) lists gnome org
Spanish (ES) daniel.mustieles (at) gmail com / Language-Team: gnome-es (at) gnome org
Ukrainian (UK) yurchor (at) ukr net

=== Current development translation status ===

In the bluefish source directory run the following command:

$ for LANG in bg cs da de el es eu fi fr gl hu it ja ko nb nl pl pt pt_BR ro ru sk sr sv ta tr uk zh_CN zh_TW ; do echo "Statistics for ${LANG}" ;for FILE in po/${LANG}.po src/plugin*/po/*${LANG}.po; do echo -n " ${FILE} " ;msgfmt --statistics ${FILE};done;done

Statistics for bg
po/bg.po 103 translated messages, 516 fuzzy translations, 297 untranslated messages.
src/plugin_about/po/bg.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/bg.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/bg.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/bg.po 224 translated messages, 214 fuzzy translations, 99 untranslated messages.
src/plugin_infbrowser/po/bg.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/bg.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/bg.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/bg.po 0 translated messages, 14 untranslated messages.
Statistics for cs
po/cs.po 881 translated messages, 25 fuzzy translations, 10 untranslated messages.
src/plugin_about/po/cs.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/cs.po 2 translated messages.
src/plugin_entities/po/cs.po 24 translated messages.
src/plugin_htmlbar/po/cs.po 537 translated messages.
src/plugin_infbrowser/po/cs.po 27 translated messages.
src/plugin_snippets/po/cs.po 60 translated messages.
src/plugin_xmltools/po/cs.po 2 translated messages.
src/plugin_zencoding/po/cs.po 14 translated messages.
Statistics for da
po/da.po 888 translated messages, 18 fuzzy translations, 10 untranslated messages.
src/plugin_about/po/da.po 17 translated messages.
src/plugin_charmap/po/da.po 2 translated messages.
src/plugin_entities/po/da.po 24 translated messages.
src/plugin_htmlbar/po/da.po 537 translated messages.
src/plugin_infbrowser/po/da.po 27 translated messages.
src/plugin_snippets/po/da.po 60 translated messages.
src/plugin_xmltools/po/da.po 2 translated messages.
src/plugin_zencoding/po/da.po 14 translated messages.
Statistics for de
po/de.po 898 translated messages, 12 fuzzy translations, 6 untranslated messages.
src/plugin_about/po/de.po 17 translated messages.
src/plugin_charmap/po/de.po 2 translated messages.
src/plugin_entities/po/de.po 24 translated messages.
src/plugin_htmlbar/po/de.po 537 translated messages.
src/plugin_infbrowser/po/de.po 27 translated messages.
src/plugin_snippets/po/de.po 60 translated messages.
src/plugin_xmltools/po/de.po 2 translated messages.
src/plugin_zencoding/po/de.po 14 translated messages.
Statistics for el
po/el.po 59 translated messages, 488 fuzzy translations, 369 untranslated messages.
src/plugin_about/po/el.po 1 translated message, 1 fuzzy translation, 15 untranslated messages.
src/plugin_charmap/po/el.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/el.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/el.po 153 translated messages, 242 fuzzy translations, 142 untranslated messages.
src/plugin_infbrowser/po/el.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/el.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/el.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/el.po 0 translated messages, 14 untranslated messages.
Statistics for es
po/es.po 888 translated messages, 18 fuzzy translations, 10 untranslated messages.
src/plugin_about/po/es.po 17 translated messages.
src/plugin_charmap/po/es.po 2 translated messages.
src/plugin_entities/po/es.po 24 translated messages.
src/plugin_htmlbar/po/es.po 537 translated messages.
src/plugin_infbrowser/po/es.po 27 translated messages.
src/plugin_snippets/po/es.po 60 translated messages.
src/plugin_xmltools/po/es.po 2 translated messages.
src/plugin_zencoding/po/es.po 14 translated messages.
Statistics for eu
po/eu.po 745 translated messages, 75 fuzzy translations, 96 untranslated messages.
src/plugin_about/po/eu.po 13 translated messages, 3 fuzzy translations, 1 untranslated message.
src/plugin_charmap/po/eu.po 2 translated messages.
src/plugin_entities/po/eu.po 24 translated messages.
src/plugin_htmlbar/po/eu.po 535 translated messages, 2 fuzzy translations.
src/plugin_infbrowser/po/eu.po 27 translated messages.
src/plugin_snippets/po/eu.po 60 translated messages.
src/plugin_xmltools/po/eu.po 2 translated messages.
src/plugin_zencoding/po/eu.po 14 translated messages.
Statistics for fi
po/fi.po 123 translated messages, 463 fuzzy translations, 330 untranslated messages.
src/plugin_about/po/fi.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/fi.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/fi.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/fi.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/fi.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/fi.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/fi.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/fi.po 0 translated messages, 14 untranslated messages.
Statistics for fr
po/fr.po 890 translated messages, 17 fuzzy translations, 9 untranslated messages.
src/plugin_about/po/fr.po 17 translated messages.
src/plugin_charmap/po/fr.po 2 translated messages.
src/plugin_entities/po/fr.po 24 translated messages.
src/plugin_htmlbar/po/fr.po 537 translated messages.
src/plugin_infbrowser/po/fr.po 27 translated messages.
src/plugin_snippets/po/fr.po 60 translated messages.
src/plugin_xmltools/po/fr.po 2 translated messages.
src/plugin_zencoding/po/fr.po 14 translated messages.
Statistics for gl
po/gl.po 785 translated messages, 60 fuzzy translations, 71 untranslated messages.
src/plugin_about/po/gl.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/gl.po 2 translated messages.
src/plugin_entities/po/gl.po 24 translated messages.
src/plugin_htmlbar/po/gl.po 536 translated messages, 1 fuzzy translation.
src/plugin_infbrowser/po/gl.po 27 translated messages.
src/plugin_snippets/po/gl.po 60 translated messages.
src/plugin_xmltools/po/gl.po 2 translated messages.
src/plugin_zencoding/po/gl.po 14 translated messages.
Statistics for hu
po/hu.po 888 translated messages, 18 fuzzy translations, 10 untranslated messages.
src/plugin_about/po/hu.po 17 translated messages.
src/plugin_charmap/po/hu.po 2 translated messages.
src/plugin_entities/po/hu.po 24 translated messages.
src/plugin_htmlbar/po/hu.po 537 translated messages.
src/plugin_infbrowser/po/hu.po 27 translated messages.
src/plugin_snippets/po/hu.po 60 translated messages.
src/plugin_xmltools/po/hu.po 2 translated messages.
src/plugin_zencoding/po/hu.po 14 translated messages.
Statistics for it
po/it.po 893 translated messages, 17 fuzzy translations, 6 untranslated messages.
src/plugin_about/po/it.po 17 translated messages.
src/plugin_charmap/po/it.po 2 translated messages.
src/plugin_entities/po/it.po 24 translated messages.
src/plugin_htmlbar/po/it.po 537 translated messages.
src/plugin_infbrowser/po/it.po 27 translated messages.
src/plugin_snippets/po/it.po 60 translated messages.
src/plugin_xmltools/po/it.po 2 translated messages.
src/plugin_zencoding/po/it.po 14 translated messages.
Statistics for ja
po/ja.po 901 translated messages, 10 fuzzy translations, 5 untranslated messages.
src/plugin_about/po/ja.po 17 translated messages.
src/plugin_charmap/po/ja.po 2 translated messages.
src/plugin_entities/po/ja.po 24 translated messages.
src/plugin_htmlbar/po/ja.po 537 translated messages.
src/plugin_infbrowser/po/ja.po 27 translated messages.
src/plugin_snippets/po/ja.po 60 translated messages.
src/plugin_xmltools/po/ja.po 2 translated messages.
src/plugin_zencoding/po/ja.po 14 translated messages.
Statistics for ko
po/ko.po 550 translated messages, 206 fuzzy translations, 160 untranslated messages.
src/plugin_about/po/ko.po 12 translated messages, 4 fuzzy translations, 1 untranslated message.
src/plugin_charmap/po/ko.po 2 translated messages.
src/plugin_entities/po/ko.po 17 translated messages, 6 fuzzy translations, 1 untranslated message.
src/plugin_htmlbar/po/ko.po 382 translated messages, 62 fuzzy translations, 93 untranslated messages.
src/plugin_infbrowser/po/ko.po 25 translated messages, 2 fuzzy translations.
src/plugin_snippets/po/ko.po 54 translated messages, 3 fuzzy translations, 3 untranslated messages.
src/plugin_xmltools/po/ko.po 2 translated messages.
src/plugin_zencoding/po/ko.po 0 translated messages, 14 untranslated messages.
Statistics for nb
po/nb.po 898 translated messages, 12 fuzzy translations, 6 untranslated messages.
src/plugin_about/po/nb.po 17 translated messages.
src/plugin_charmap/po/nb.po 2 translated messages.
src/plugin_entities/po/nb.po 24 translated messages.
src/plugin_htmlbar/po/nb.po 537 translated messages.
src/plugin_infbrowser/po/nb.po 27 translated messages.
src/plugin_snippets/po/nb.po 60 translated messages.
src/plugin_xmltools/po/nb.po 2 translated messages.
src/plugin_zencoding/po/nb.po 14 translated messages.
Statistics for nl
po/nl.po 893 translated messages, 17 fuzzy translations, 6 untranslated messages.
src/plugin_about/po/nl.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/nl.po 2 translated messages.
src/plugin_entities/po/nl.po 24 translated messages.
src/plugin_htmlbar/po/nl.po 537 translated messages.
src/plugin_infbrowser/po/nl.po 27 translated messages.
src/plugin_snippets/po/nl.po 60 translated messages.
src/plugin_xmltools/po/nl.po 2 translated messages.
src/plugin_zencoding/po/nl.po 14 translated messages.
Statistics for pl
po/pl.po 888 translated messages, 18 fuzzy translations, 10 untranslated messages.
src/plugin_about/po/pl.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/pl.po 2 translated messages.
src/plugin_entities/po/pl.po 24 translated messages.
src/plugin_htmlbar/po/pl.po 537 translated messages.
src/plugin_infbrowser/po/pl.po 27 translated messages.
src/plugin_snippets/po/pl.po 60 translated messages.
src/plugin_xmltools/po/pl.po 2 translated messages.
src/plugin_zencoding/po/pl.po 14 translated messages.
Statistics for pt
po/pt.po 898 translated messages, 12 fuzzy translations, 6 untranslated messages.
src/plugin_about/po/pt.po 13 translated messages, 3 fuzzy translations, 1 untranslated message.
src/plugin_charmap/po/pt.po 2 translated messages.
src/plugin_entities/po/pt.po 24 translated messages.
src/plugin_htmlbar/po/pt.po 535 translated messages, 2 fuzzy translations.
src/plugin_infbrowser/po/pt.po 27 translated messages.
src/plugin_snippets/po/pt.po 60 translated messages.
src/plugin_xmltools/po/pt.po 2 translated messages.
src/plugin_zencoding/po/pt.po 14 translated messages.
Statistics for pt_BR
po/pt_BR.po 898 translated messages, 12 fuzzy translations, 6 untranslated messages.
src/plugin_about/po/pt_BR.po 17 translated messages.
src/plugin_charmap/po/pt_BR.po 2 translated messages.
src/plugin_entities/po/pt_BR.po 24 translated messages.
src/plugin_htmlbar/po/pt_BR.po 537 translated messages.
src/plugin_infbrowser/po/pt_BR.po 27 translated messages.
src/plugin_snippets/po/pt_BR.po 60 translated messages.
src/plugin_xmltools/po/pt_BR.po 2 translated messages.
src/plugin_zencoding/po/pt_BR.po 14 translated messages.
Statistics for ro
po/ro.po 88 translated messages, 489 fuzzy translations, 339 untranslated messages.
src/plugin_about/po/ro.po 1 translated message, 16 untranslated messages.
src/plugin_charmap/po/ro.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/ro.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/ro.po 71 translated messages, 293 fuzzy translations, 173 untranslated messages.
src/plugin_infbrowser/po/ro.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/ro.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/ro.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/ro.po 0 translated messages, 14 untranslated messages.
Statistics for ru
po/ru.po 916 translated messages.
src/plugin_about/po/ru.po 17 translated messages.
src/plugin_charmap/po/ru.po 2 translated messages.
src/plugin_entities/po/ru.po 24 translated messages.
src/plugin_htmlbar/po/ru.po 537 translated messages.
src/plugin_infbrowser/po/ru.po 27 translated messages.
src/plugin_snippets/po/ru.po 60 translated messages.
src/plugin_xmltools/po/ru.po 2 translated messages.
src/plugin_zencoding/po/ru.po 14 translated messages.
Statistics for sk
po/sk.po 189 translated messages, 474 fuzzy translations, 253 untranslated messages.
src/plugin_about/po/sk.po 0 translated messages, 4 fuzzy translations, 13 untranslated messages.
src/plugin_charmap/po/sk.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/sk.po 0 translated messages, 17 fuzzy translations, 7 untranslated messages.
src/plugin_htmlbar/po/sk.po 248 translated messages, 173 fuzzy translations, 116 untranslated messages.
src/plugin_infbrowser/po/sk.po 0 translated messages, 1 fuzzy translation, 26 untranslated messages.
src/plugin_snippets/po/sk.po 2 translated messages, 29 fuzzy translations, 29 untranslated messages.
src/plugin_xmltools/po/sk.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/sk.po 0 translated messages, 14 untranslated messages.
Statistics for sr
po/sr.po 115 translated messages, 510 fuzzy translations, 291 untranslated messages.
src/plugin_about/po/sr.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/sr.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/sr.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/sr.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/sr.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/sr.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/sr.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/sr.po 0 translated messages, 14 untranslated messages.
Statistics for sv
po/sv.po 115 translated messages, 513 fuzzy translations, 288 untranslated messages.
src/plugin_about/po/sv.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/sv.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/sv.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/sv.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/sv.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/sv.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/sv.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/sv.po 0 translated messages, 14 untranslated messages.
Statistics for ta
po/ta.po 116 translated messages, 513 fuzzy translations, 287 untranslated messages.
src/plugin_about/po/ta.po 0 translated messages, 4 fuzzy translations, 13 untranslated messages.
src/plugin_charmap/po/ta.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/ta.po 0 translated messages, 17 fuzzy translations, 7 untranslated messages.
src/plugin_htmlbar/po/ta.po 245 translated messages, 174 fuzzy translations, 118 untranslated messages.
src/plugin_infbrowser/po/ta.po 0 translated messages, 1 fuzzy translation, 26 untranslated messages.
src/plugin_snippets/po/ta.po 2 translated messages, 29 fuzzy translations, 29 untranslated messages.
src/plugin_xmltools/po/ta.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/ta.po 0 translated messages, 14 untranslated messages.
Statistics for tr
po/tr.po 893 translated messages, 17 fuzzy translations, 6 untranslated messages.
src/plugin_about/po/tr.po 17 translated messages.
src/plugin_charmap/po/tr.po 2 translated messages.
src/plugin_entities/po/tr.po 24 translated messages.
src/plugin_htmlbar/po/tr.po 537 translated messages.
src/plugin_infbrowser/po/tr.po 27 translated messages.
src/plugin_snippets/po/tr.po 60 translated messages.
src/plugin_xmltools/po/tr.po 2 translated messages.
src/plugin_zencoding/po/tr.po 14 translated messages.
Statistics for uk
po/uk.po 888 translated messages, 18 fuzzy translations, 10 untranslated messages.
src/plugin_about/po/uk.po 17 translated messages.
src/plugin_charmap/po/uk.po 2 translated messages.
src/plugin_entities/po/uk.po 24 translated messages.
src/plugin_htmlbar/po/uk.po 537 translated messages.
src/plugin_infbrowser/po/uk.po 27 translated messages.
src/plugin_snippets/po/uk.po 60 translated messages.
src/plugin_xmltools/po/uk.po 2 translated messages.
src/plugin_zencoding/po/uk.po 14 translated messages.
Statistics for zh_CN
po/zh_CN.po 772 translated messages, 68 fuzzy translations, 76 untranslated messages.
src/plugin_about/po/zh_CN.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/zh_CN.po 2 translated messages.
src/plugin_entities/po/zh_CN.po 24 translated messages.
src/plugin_htmlbar/po/zh_CN.po 536 translated messages, 1 fuzzy translation.
src/plugin_infbrowser/po/zh_CN.po 27 translated messages.
src/plugin_snippets/po/zh_CN.po 60 translated messages.
src/plugin_xmltools/po/zh_CN.po 2 translated messages.
src/plugin_zencoding/po/zh_CN.po 14 translated messages.
Statistics for zh_TW
po/zh_TW.po 115 translated messages, 510 fuzzy translations, 291 untranslated messages.
src/plugin_about/po/zh_TW.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/zh_TW.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/zh_TW.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/zh_TW.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/zh_TW.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/zh_TW.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/zh_TW.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/zh_TW.po 0 translated messages, 14 untranslated messages.

== Notes and references ==
<references/>

[[Category:i18n]]

Translations

2024-09-13T15:05:07Z

OlivierSessink:

== Translations ==

Please send a message to the developer's list if you have questions, suggestions or would like to help with translations. By all means, don't wait for someone to give you the OK to start translating. Here are some instructions on [[How To Translate]].

== Current translation teams ==

It is good if there are multiple people for every language, so if anybody is on holidays or something and we want to do a Bluefish release we can have all languages updated, so please work in teams.

=== Active translators / teams ===
These translations are kept up to date (last updated Feb 13 2014):

Basque (EU) dooteo (at) euskalgnu org / Language-Team: itzulpena (at) euskalgnu org
Brazilian Portuguese (PT_BR) esfingemetal (at) gmail com
Catalan (CA) monica (at) probeta.net
Chinese (ZH_CN) mzf9527 (at) gmail com
Czech (CS) marek (at) manet cz / Language-Team: gnome-cs-list (at) gnome org
Danish (DA) fc (at) stilheden net / Language Team: dansk (at) dansk-gruppen dk
Dutch (NL) olivier (at) bluefish openoffice nl
Farsi (FA) Paymon Menhadji
French (FR) falsetti (at) clansco org
Galician (GL) correo.xmgz (at) gmail com
German (DE) Ralf.Kestler (at) gmx net, linux (at) drmartinus de
Hungarian (HU) urbalazs (at) gmail com / Language-Team: hu (at) li org
Italian (IT) bellingeri (at) netguru it
Japanese (JA) hmatrjp (at) users sourceforge jp
Norwegian (NB) chris (at) tellefsen net
Nynorsk (NN) l10n (at) landro net
Polish (PL) dawajpoczte (at) gmail com
Russian (RU) george (at) altlinux org / Language-Team: gnome-cyr (at) lists gnome org
Spanish (ES) daniel.mustieles (at) gmail com / Language-Team: gnome-es (at) gnome org
Ukrainian (UK) yurchor (at) ukr net

=== Current development translation status ===

In the bluefish source directory run the following command:

$ for LANG in bg cs da de el es eu fi fr gl hu it ja ko nb nl pl pt pt_BR ro ru sk sr sv ta tr uk zh_CN zh_TW ; do echo "Statistics for ${LANG}" ;for FILE in po/${LANG}.po src/plugin*/po/*${LANG}.po; do echo -n " ${FILE} " ;msgfmt --statistics ${FILE};done;done

Statistics for bg
po/bg.po 102 translated messages, 505 fuzzy translations, 289 untranslated messages.
src/plugin_about/po/bg.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/bg.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/bg.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/bg.po 224 translated messages, 214 fuzzy translations, 99 untranslated messages.
src/plugin_infbrowser/po/bg.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/bg.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/bg.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/bg.po 0 translated messages, 14 untranslated messages.
Statistics for cs
po/cs.po 883 translated messages, 10 fuzzy translations, 3 untranslated messages.
src/plugin_about/po/cs.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/cs.po 2 translated messages.
src/plugin_entities/po/cs.po 24 translated messages.
src/plugin_htmlbar/po/cs.po 537 translated messages.
src/plugin_infbrowser/po/cs.po 27 translated messages.
src/plugin_snippets/po/cs.po 60 translated messages.
src/plugin_xmltools/po/cs.po 2 translated messages.
src/plugin_zencoding/po/cs.po 14 translated messages.
Statistics for da
po/da.po 890 translated messages, 3 fuzzy translations, 3 untranslated messages.
src/plugin_about/po/da.po 17 translated messages.
src/plugin_charmap/po/da.po 2 translated messages.
src/plugin_entities/po/da.po 24 translated messages.
src/plugin_htmlbar/po/da.po 537 translated messages.
src/plugin_infbrowser/po/da.po 27 translated messages.
src/plugin_snippets/po/da.po 60 translated messages.
src/plugin_xmltools/po/da.po 2 translated messages.
src/plugin_zencoding/po/da.po 14 translated messages.
Statistics for de
po/de.po 904 translated messages.
src/plugin_about/po/de.po 17 translated messages.
src/plugin_charmap/po/de.po 2 translated messages.
src/plugin_entities/po/de.po 24 translated messages.
src/plugin_htmlbar/po/de.po 537 translated messages.
src/plugin_infbrowser/po/de.po 27 translated messages.
src/plugin_snippets/po/de.po 60 translated messages.
src/plugin_xmltools/po/de.po 2 translated messages.
src/plugin_zencoding/po/de.po 14 translated messages.
Statistics for el
po/el.po 58 translated messages, 478 fuzzy translations, 360 untranslated messages.
src/plugin_about/po/el.po 1 translated message, 1 fuzzy translation, 15 untranslated messages.
src/plugin_charmap/po/el.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/el.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/el.po 153 translated messages, 242 fuzzy translations, 142 untranslated messages.
src/plugin_infbrowser/po/el.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/el.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/el.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/el.po 0 translated messages, 14 untranslated messages.
Statistics for es
po/es.po 890 translated messages, 3 fuzzy translations, 3 untranslated messages.
src/plugin_about/po/es.po 17 translated messages.
src/plugin_charmap/po/es.po 2 translated messages.
src/plugin_entities/po/es.po 24 translated messages.
src/plugin_htmlbar/po/es.po 537 translated messages.
src/plugin_infbrowser/po/es.po 27 translated messages.
src/plugin_snippets/po/es.po 60 translated messages.
src/plugin_xmltools/po/es.po 2 translated messages.
src/plugin_zencoding/po/es.po 14 translated messages.
Statistics for eu
po/eu.po 743 translated messages, 64 fuzzy translations, 89 untranslated messages.
src/plugin_about/po/eu.po 13 translated messages, 3 fuzzy translations, 1 untranslated message.
src/plugin_charmap/po/eu.po 2 translated messages.
src/plugin_entities/po/eu.po 24 translated messages.
src/plugin_htmlbar/po/eu.po 535 translated messages, 2 fuzzy translations.
src/plugin_infbrowser/po/eu.po 27 translated messages.
src/plugin_snippets/po/eu.po 60 translated messages.
src/plugin_xmltools/po/eu.po 2 translated messages.
src/plugin_zencoding/po/eu.po 14 translated messages.
Statistics for fi
po/fi.po 123 translated messages, 454 fuzzy translations, 319 untranslated messages.
src/plugin_about/po/fi.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/fi.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/fi.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/fi.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/fi.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/fi.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/fi.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/fi.po 0 translated messages, 14 untranslated messages.
Statistics for fr
po/fr.po 894 translated messages, 6 fuzzy translations, 4 untranslated messages.
src/plugin_about/po/fr.po 17 translated messages.
src/plugin_charmap/po/fr.po 2 translated messages.
src/plugin_entities/po/fr.po 24 translated messages.
src/plugin_htmlbar/po/fr.po 537 translated messages.
src/plugin_infbrowser/po/fr.po 27 translated messages.
src/plugin_snippets/po/fr.po 60 translated messages.
src/plugin_xmltools/po/fr.po 2 translated messages.
src/plugin_zencoding/po/fr.po 14 translated messages.
Statistics for gl
po/gl.po 787 translated messages, 45 fuzzy translations, 64 untranslated messages.
src/plugin_about/po/gl.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/gl.po 2 translated messages.
src/plugin_entities/po/gl.po 24 translated messages.
src/plugin_htmlbar/po/gl.po 536 translated messages, 1 fuzzy translation.
src/plugin_infbrowser/po/gl.po 27 translated messages.
src/plugin_snippets/po/gl.po 60 translated messages.
src/plugin_xmltools/po/gl.po 2 translated messages.
src/plugin_zencoding/po/gl.po 14 translated messages.
Statistics for hu
po/hu.po 890 translated messages, 3 fuzzy translations, 3 untranslated messages.
src/plugin_about/po/hu.po 17 translated messages.
src/plugin_charmap/po/hu.po 2 translated messages.
src/plugin_entities/po/hu.po 24 translated messages.
src/plugin_htmlbar/po/hu.po 537 translated messages.
src/plugin_infbrowser/po/hu.po 27 translated messages.
src/plugin_snippets/po/hu.po 60 translated messages.
src/plugin_xmltools/po/hu.po 2 translated messages.
src/plugin_zencoding/po/hu.po 14 translated messages.
Statistics for it
po/it.po 898 translated messages.
src/plugin_about/po/it.po 17 translated messages.
src/plugin_charmap/po/it.po 2 translated messages.
src/plugin_entities/po/it.po 24 translated messages.
src/plugin_htmlbar/po/it.po 537 translated messages.
src/plugin_infbrowser/po/it.po 27 translated messages.
src/plugin_snippets/po/it.po 60 translated messages.
src/plugin_xmltools/po/it.po 2 translated messages.
src/plugin_zencoding/po/it.po 14 translated messages.
Statistics for ja
po/ja.po 886 translated messages.
src/plugin_about/po/ja.po 17 translated messages.
src/plugin_charmap/po/ja.po 2 translated messages.
src/plugin_entities/po/ja.po 24 translated messages.
src/plugin_htmlbar/po/ja.po 537 translated messages.
src/plugin_infbrowser/po/ja.po 27 translated messages.
src/plugin_snippets/po/ja.po 60 translated messages.
src/plugin_xmltools/po/ja.po 2 translated messages.
src/plugin_zencoding/po/ja.po 14 translated messages.
Statistics for ko
po/ko.po 548 translated messages, 197 fuzzy translations, 151 untranslated messages.
src/plugin_about/po/ko.po 12 translated messages, 4 fuzzy translations, 1 untranslated message.
src/plugin_charmap/po/ko.po 2 translated messages.
src/plugin_entities/po/ko.po 17 translated messages, 6 fuzzy translations, 1 untranslated message.
src/plugin_htmlbar/po/ko.po 382 translated messages, 62 fuzzy translations, 93 untranslated messages.
src/plugin_infbrowser/po/ko.po 25 translated messages, 2 fuzzy translations.
src/plugin_snippets/po/ko.po 54 translated messages, 3 fuzzy translations, 3 untranslated messages.
src/plugin_xmltools/po/ko.po 2 translated messages.
src/plugin_zencoding/po/ko.po 0 translated messages, 14 untranslated messages.
Statistics for nb
po/nb.po 904 translated messages.
src/plugin_about/po/nb.po 17 translated messages.
src/plugin_charmap/po/nb.po 2 translated messages.
src/plugin_entities/po/nb.po 24 translated messages.
src/plugin_htmlbar/po/nb.po 537 translated messages.
src/plugin_infbrowser/po/nb.po 27 translated messages.
src/plugin_snippets/po/nb.po 60 translated messages.
src/plugin_xmltools/po/nb.po 2 translated messages.
src/plugin_zencoding/po/nb.po 14 translated messages.
Statistics for nl
po/nl.po 899 translated messages.
src/plugin_about/po/nl.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/nl.po 2 translated messages.
src/plugin_entities/po/nl.po 24 translated messages.
src/plugin_htmlbar/po/nl.po 537 translated messages.
src/plugin_infbrowser/po/nl.po 27 translated messages.
src/plugin_snippets/po/nl.po 60 translated messages.
src/plugin_xmltools/po/nl.po 2 translated messages.
src/plugin_zencoding/po/nl.po 14 translated messages.
Statistics for pl
po/pl.po 890 translated messages, 3 fuzzy translations, 3 untranslated messages.
src/plugin_about/po/pl.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/pl.po 2 translated messages.
src/plugin_entities/po/pl.po 24 translated messages.
src/plugin_htmlbar/po/pl.po 537 translated messages.
src/plugin_infbrowser/po/pl.po 27 translated messages.
src/plugin_snippets/po/pl.po 60 translated messages.
src/plugin_xmltools/po/pl.po 2 translated messages.
src/plugin_zencoding/po/pl.po 14 translated messages.
Statistics for pt
po/pt.po 904 translated messages.
src/plugin_about/po/pt.po 13 translated messages, 3 fuzzy translations, 1 untranslated message.
src/plugin_charmap/po/pt.po 2 translated messages.
src/plugin_entities/po/pt.po 24 translated messages.
src/plugin_htmlbar/po/pt.po 535 translated messages, 2 fuzzy translations.
src/plugin_infbrowser/po/pt.po 27 translated messages.
src/plugin_snippets/po/pt.po 60 translated messages.
src/plugin_xmltools/po/pt.po 2 translated messages.
src/plugin_zencoding/po/pt.po 14 translated messages.
Statistics for pt_BR
po/pt_BR.po 904 translated messages.
src/plugin_about/po/pt_BR.po 17 translated messages.
src/plugin_charmap/po/pt_BR.po 2 translated messages.
src/plugin_entities/po/pt_BR.po 24 translated messages.
src/plugin_htmlbar/po/pt_BR.po 537 translated messages.
src/plugin_infbrowser/po/pt_BR.po 27 translated messages.
src/plugin_snippets/po/pt_BR.po 60 translated messages.
src/plugin_xmltools/po/pt_BR.po 2 translated messages.
src/plugin_zencoding/po/pt_BR.po 14 translated messages.
Statistics for ro
po/ro.po 85 translated messages, 480 fuzzy translations, 331 untranslated messages.
src/plugin_about/po/ro.po 1 translated message, 16 untranslated messages.
src/plugin_charmap/po/ro.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/ro.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/ro.po 71 translated messages, 293 fuzzy translations, 173 untranslated messages.
src/plugin_infbrowser/po/ro.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/ro.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/ro.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/ro.po 0 translated messages, 14 untranslated messages.
Statistics for ru
po/ru.po 916 translated messages.
src/plugin_about/po/ru.po 17 translated messages.
src/plugin_charmap/po/ru.po 2 translated messages.
src/plugin_entities/po/ru.po 24 translated messages.
src/plugin_htmlbar/po/ru.po 537 translated messages.
src/plugin_infbrowser/po/ru.po 27 translated messages.
src/plugin_snippets/po/ru.po 60 translated messages.
src/plugin_xmltools/po/ru.po 2 translated messages.
src/plugin_zencoding/po/ru.po 14 translated messages.
Statistics for sk
po/sk.po 187 translated messages, 463 fuzzy translations, 246 untranslated messages.
src/plugin_about/po/sk.po 0 translated messages, 4 fuzzy translations, 13 untranslated messages.
src/plugin_charmap/po/sk.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/sk.po 0 translated messages, 17 fuzzy translations, 7 untranslated messages.
src/plugin_htmlbar/po/sk.po 248 translated messages, 173 fuzzy translations, 116 untranslated messages.
src/plugin_infbrowser/po/sk.po 0 translated messages, 1 fuzzy translation, 26 untranslated messages.
src/plugin_snippets/po/sk.po 2 translated messages, 29 fuzzy translations, 29 untranslated messages.
src/plugin_xmltools/po/sk.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/sk.po 0 translated messages, 14 untranslated messages.
Statistics for sr
po/sr.po 114 translated messages, 499 fuzzy translations, 283 untranslated messages.
src/plugin_about/po/sr.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/sr.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/sr.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/sr.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/sr.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/sr.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/sr.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/sr.po 0 translated messages, 14 untranslated messages.
Statistics for sv
po/sv.po 114 translated messages, 502 fuzzy translations, 280 untranslated messages.
src/plugin_about/po/sv.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/sv.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/sv.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/sv.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/sv.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/sv.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/sv.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/sv.po 0 translated messages, 14 untranslated messages.
Statistics for ta
po/ta.po 115 translated messages, 502 fuzzy translations, 279 untranslated messages.
src/plugin_about/po/ta.po 0 translated messages, 4 fuzzy translations, 13 untranslated messages.
src/plugin_charmap/po/ta.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/ta.po 0 translated messages, 17 fuzzy translations, 7 untranslated messages.
src/plugin_htmlbar/po/ta.po 245 translated messages, 174 fuzzy translations, 118 untranslated messages.
src/plugin_infbrowser/po/ta.po 0 translated messages, 1 fuzzy translation, 26 untranslated messages.
src/plugin_snippets/po/ta.po 2 translated messages, 29 fuzzy translations, 29 untranslated messages.
src/plugin_xmltools/po/ta.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/ta.po 0 translated messages, 14 untranslated messages.
Statistics for tr
po/tr.po 898 translated messages.
src/plugin_about/po/tr.po 17 translated messages.
src/plugin_charmap/po/tr.po 2 translated messages.
src/plugin_entities/po/tr.po 24 translated messages.
src/plugin_htmlbar/po/tr.po 537 translated messages.
src/plugin_infbrowser/po/tr.po 27 translated messages.
src/plugin_snippets/po/tr.po 60 translated messages.
src/plugin_xmltools/po/tr.po 2 translated messages.
src/plugin_zencoding/po/tr.po 14 translated messages.
Statistics for uk
po/uk.po 890 translated messages, 3 fuzzy translations, 3 untranslated messages.
src/plugin_about/po/uk.po 17 translated messages.
src/plugin_charmap/po/uk.po 2 translated messages.
src/plugin_entities/po/uk.po 24 translated messages.
src/plugin_htmlbar/po/uk.po 537 translated messages.
src/plugin_infbrowser/po/uk.po 27 translated messages.
src/plugin_snippets/po/uk.po 60 translated messages.
src/plugin_xmltools/po/uk.po 2 translated messages.
src/plugin_zencoding/po/uk.po 14 translated messages.
Statistics for zh_CN
po/zh_CN.po 774 translated messages, 53 fuzzy translations, 69 untranslated messages.
src/plugin_about/po/zh_CN.po 16 translated messages, 1 fuzzy translation.
src/plugin_charmap/po/zh_CN.po 2 translated messages.
src/plugin_entities/po/zh_CN.po 24 translated messages.
src/plugin_htmlbar/po/zh_CN.po 536 translated messages, 1 fuzzy translation.
src/plugin_infbrowser/po/zh_CN.po 27 translated messages.
src/plugin_snippets/po/zh_CN.po 60 translated messages.
src/plugin_xmltools/po/zh_CN.po 2 translated messages.
src/plugin_zencoding/po/zh_CN.po 14 translated messages.
Statistics for zh_TW
po/zh_TW.po 114 translated messages, 499 fuzzy translations, 283 untranslated messages.
src/plugin_about/po/zh_TW.po 1 translated message, 4 fuzzy translations, 12 untranslated messages.
src/plugin_charmap/po/zh_TW.po 0 translated messages, 2 untranslated messages.
src/plugin_entities/po/zh_TW.po 0 translated messages, 24 untranslated messages.
src/plugin_htmlbar/po/zh_TW.po 224 translated messages, 215 fuzzy translations, 98 untranslated messages.
src/plugin_infbrowser/po/zh_TW.po 0 translated messages, 27 untranslated messages.
src/plugin_snippets/po/zh_TW.po 0 translated messages, 60 untranslated messages.
src/plugin_xmltools/po/zh_TW.po 0 translated messages, 2 untranslated messages.
src/plugin_zencoding/po/zh_TW.po 0 translated messages, 14 untranslated messages.

== Notes and references ==
<references/>

[[Category:i18n]]

How To Translate

2024-09-13T14:59:53Z

OlivierSessink:

== Translations ==
(this How To is based on Bluefish Manual page : [[Man 1 ch12s08]])
=== 1. Introduction ===
Bluefish has been translated into more than 15 different languages and this is only the beginning.

Translation process is not a difficult task but you will need some time because there are more than one thousand strings to be translated. <br />
There are seven translation directories in Bluefish development branch, one for main program and one for each plugin:
* po/
* src/plugin_about/po/
* src/plugin_charmap/po/
* src/plugin_entities/po/
* src/plugin_htmlbar/po/
* src/plugin_infbrowser/po/
* src/plugin_snippets/po/
* src/plugin_zencoding/po/
The good news are you don't need to be a programmer to make Bluefish speak your language and the only tool you need is a text editor (bluefish for example) or Poedit or the gnome translation editor. Bluefish uses po (Portable Object) files. A po file is just a plain text file that you can edit with your favorite text editor.

=== 2. PO files basics ===
In a typical po file there are five major types of entries:

# Those which begin with "#:" showing the places in the source code that contains the string being translated (there may be one or more) as: '<nowiki>#: ../src/about.c:123</nowiki>'
# Those which begin with "#," containing some flags (not always present) as: '<nowiki>#, c-format</nowiki>'
# Those which begin with "msgid" containing the English string being translated (it may be spanned in several lines) as: 'msgid "Authentication is required for %s."'
# Those which begin with "msgstr" containing the translated string as: 'msgstr "Une autorisation est requise pour accéder à %s."'
# Those which begin with "#~ " containing obsolete strings as: '<nowiki>#~ msgid "Save document as"</nowiki>'

[[Image:Man1_warning.png]] When an entry is tagged as fuzzy (i.e. when the line begins with "<nowiki>#, fuzzy</nowiki>"), that means it is probably incorrect.

[[Image:Man1_warning.png]] You have to make sure the translation is correct and then delete either the "<nowiki>#, fuzzy</nowiki>" line if this is the only flag on the line, or the ", fuzzy" part of the line if there are some other flags on the same line, like in "<nowiki>#, fuzzy, c-format</nowiki>".

[[Image:Man1_warning.png]] Remember that as long as a translation is marked "fuzzy", it will NOT actually be used!

[[Image:Man1_warning.png]] As far as obsolete strings are concerned, it is up to you to decide if you want to remove them. On one hand they can be reused in a latter version of the po file, on the other hand they make the po file bigger.

Hence, your task as a translator is to:

# Translate all empty msgstr entries
# Check all fuzzy entries, correct them if they are wrong and remove all fuzzy tags
# Optionally, remove obsolete strings
# Check that the po file ends with a blank line

=== 3. Shortcut keys ===
Shortcut keys, known as hotkeys or even accelerator keys, are defined as follows (look at the underscore, please):

<nowiki># src/toolbars.c:482</nowiki>
<nowiki>#: ../src/filebrowser.c:1453</nowiki>
msgid "/_Refresh"
msgstr "/_Actualizar"

It means that in the English locale the user have to press '''Alt'''+'''R''' to activate this particular GUI element. On the other hand if your locale is Spanish your shortcut key will be '''Alt'''+'''A'''.

[[Image:Man1_warning.png]] You have to keep in mind that two GUI elements must not have the same shortcut key at the same level.

=== 4. Retriving last Bluefish version===
* 1. In your working space directory (eg ~/tranlations) run: <br />
svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/
that create the Bluefish SVN directory
* 2. '''cd bluefish/''' and for first installation run '''./autogen.sh'''
* 3. run '''./configure''' and '''make'''
* 4. you can now update all files.
see also [[Sending_Patches#Notes_for_translators]]
=== 5. Sending your translation ===
see also [[Sending_Patches#Special_notes_for_translators]]
* 1. update your SVN copy. In Bluefish/ dirctory run:
svn update
* 2. The following step is not necessary but it will help you finding issues, which must be fixed, before your changes can be committed to the subversion tree. It requires an installation of the gettext tools. Please change `your_lang` with your language code ;)
find . -name your_lang.po | xargs msgcat --use-first -o - | msgfmt -o /dev/null --statistics -
* 3. create the tarball:
find . -name your_lang.po | xargs tar -cjf your_lang.tar.bz2
* 4. send the tarball

Building a native (no X11) MacOSX binary

2024-08-11T18:26:42Z

OlivierSessink:

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ PATH=~/.new_local/bin/:$PATH
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3 shared-mime-info enchant

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

for bundling you need https://gitlab.gnome.org/GNOME/gtk-mac-bundler as well. Download it and run ''make install''

jhbuild shell
cd /to/your/bluefish/source/path
./autogen.sh
make -j6 -f Makefile.osxapp

(the -j6 is for a 6core computer)

this creates a Bluefish.app on your Desktop

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project is used to create a bundle with all libraries, it is called during the above mentioned make command. The config file macosx/bluefish.bundle and macosx/Info.plist should be updated for every version of Bluefish.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-11T18:24:51Z

OlivierSessink: /* Getting a native gtk */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ PATH=~/.new_local/bin/:$PATH
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3 shared-mime-info

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

for bundling you need https://gitlab.gnome.org/GNOME/gtk-mac-bundler as well. Download it and run ''make install''

jhbuild shell
cd /to/your/bluefish/source/path
./autogen.sh
make -j6 -f Makefile.osxapp

(the -j6 is for a 6core computer)

this creates a Bluefish.app on your Desktop

== Additional modules for more functionality ==

it's not clear why certain modules defined in ~/Source/jhbuild/modulesets are accepted by jhbuild and others are not?

$ jhbuild enchant

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-11T14:52:52Z

OlivierSessink:

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3 shared-mime-info

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

for bundling you need https://gitlab.gnome.org/GNOME/gtk-mac-bundler as well. Download it and run ''make install''

jhbuild shell
cd /to/your/bluefish/source/path
./autogen.sh
make -j6 -f Makefile.osxapp

(the -j6 is for a 6core computer)

this creates a Bluefish.app on your Desktop

== Additional modules for more functionality ==

it's not clear why certain modules defined in ~/Source/jhbuild/modulesets are accepted by jhbuild and others are not?

$ jhbuild enchant

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-10T17:52:05Z

OlivierSessink: /* Building Bluefish with Makefile.osxapp */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3 shared-mime-info

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
cd /to/your/bluefish/source/path
./autogen.sh
make -j6 -f Makefile.osxapp

(the -j6 is for a 6core computer)

this creates a Bluefish.app on your Desktop

== Additional modules for more functionality ==

it's not clear why certain modules defined in ~/Source/jhbuild/modulesets are accepted by jhbuild and others are not?

$ jhbuild enchant

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-10T17:27:13Z

OlivierSessink: /* Building Bluefish with Makefile.osxapp */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3 shared-mime-info

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
cd /to/your/bluefish/source/path
./autogen.sh
make -j6 -f Makefile.osxapp

(the -j6 is for a 6core computer)

this creates a Bluefish.app on your Desktop

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-10T15:02:41Z

OlivierSessink: /* Getting a native gtk */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3 shared-mime-info

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries, so this will crash on systems that do not have a gtk library installed on the system.

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-10T15:00:43Z

OlivierSessink: /* Getting a native gtk */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

For full functionality also install some other related packages:

$ jhbuild build shared-mime-info gnome-icon-theme gtk-engines tango-icon-theme

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries, so this will crash on systems that do not have a gtk library installed on the system.

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-10T14:59:32Z

OlivierSessink:

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

For full functionality also install some other related packages:

$ jhbuild build shared-mime-info gnome-mime-data gnome-icon-theme gtk-engines tango-icon-theme

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries, so this will crash on systems that do not have a gtk library installed on the system.

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-10T14:58:42Z

OlivierSessink: /* Getting a native gtk */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-python meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

For full functionality also install some other related packages:

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries, so this will crash on systems that do not have a gtk library installed on the system.

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-08T21:00:27Z

OlivierSessink: /* Creating a working bundle Bluefish.app */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries, so this will crash on systems that do not have a gtk library installed on the system.

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-08T20:45:52Z

OlivierSessink:

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries, so this will crash on systems that do not have a gtk library installed on the system.

== Creating a working bundle Bluefish.app ==

The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler.

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-08T20:44:30Z

OlivierSessink: /* Build with jhbuild (work in progress) */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries. The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler

== Build with jhbuild (work in progress, THIS IS NOT YET WORKING) ==

==== Building with a jhbuild configuration ====

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-08T20:44:05Z

OlivierSessink: /* Building Bluefish with Makefile.osxapp */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

this creates a Bluefish.app without any libraries. The gtk-mac-bundler project can be used to create a bundle with all libraries. The config file macosx/bluefish.bundle should be updated for the latest version of gtk-mac-bundler

== Build with jhbuild (work in progress) ==

=== Building with a jhbuild configuration ===

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-06T13:01:20Z

OlivierSessink: /* Getting a native gtk */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

First follow the Quick start as described here:
https://gitlab.gnome.org/GNOME/gtk-osx/-/wikis/home#quick-start
follow the instructions to get the gtk core up and running
$ ./gtk-osx-setup.sh
$ jhbuild bootstrap-gtk-osx
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

== Build with jhbuild (work in progress) ==

=== Building with a jhbuild configuration ===

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-05T15:44:29Z

OlivierSessink: /* Getting a native gtk */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here: https://www.gtk.org/docs/installations/macos/

first use the provided script: https://gitlab.gnome.org/GNOME/gtk-osx/-/blob/master/gtk-osx-setup.sh

follow the instructions to get the gtk core up and running
$ jhbuild bootstrap
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

find help on https://gitlab.gnome.org/GNOME/gtk-mac-integration/

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

== Build with jhbuild (work in progress) ==

=== Building with a jhbuild configuration ===

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-05T15:38:17Z

OlivierSessink: /* Building Bluefish with Makefile.osxapp */

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here:
http://gtk-osx.sourceforge.net/

follow the instructions to get the gtk core up and running
$ jhbuild bootstrap
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -j6 -f Makefile.osxapp
make -j6 -f Makefile.osxapp install
(the -j6 is for a 6core computer)

== Build with jhbuild (work in progress) ==

=== Building with a jhbuild configuration ===

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Building a native (no X11) MacOSX binary

2024-08-05T15:35:33Z

OlivierSessink: update for gtk3

This is work in progress.

== Getting a native gtk ==
A lot of information can be found here:
http://gtk-osx.sourceforge.net/

follow the instructions to get the gtk core up and running
$ jhbuild bootstrap
$ jhbuild build meta-gtk-osx-bootstrap
$ jhbuild build meta-gtk-osx-python
$ jhbuild build meta-gtk-osx-gtk3

== Building Bluefish with Makefile.osxapp ==

jhbuild shell
./autogen.sh
make -f Makefile.osxapp
make -f Makefile.osxapp install

== Build with jhbuild (work in progress) ==

=== Building with a jhbuild configuration ===

a jhbuild section for bluefish looks like this:
--------------------------------
<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
----------------------------------

or a section for SVN:
----------------------------------
<repository type="svn" name="bluefish-svn" default="yes" href="https://bluefish.svn.sourceforge.net/svnroot/" />
<autotools id="bluefish-svn" autogen-sh="./configure" autogenargs="--disable-nls" >
<branch repo="bluefish-svn" module="bluefish/trunk/bluefish"/>
<dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
<dep package="ige-mac-integration"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>
--------------------------------------
this section will fail the first time, choose 4 (enter shell), run
./autogen.sh
exit and choose 1 (rerun configure)

== Creating a package ==

The quick and dirty way: open an existing Bluefish.dmg, convert it to writable dmg, copy the contents of the newly built Bluefish.app into the dmg, convert it back to compressed.

Some packages that should be installed (with jhbuild) as well:

shared-mime-info
meta-gtk-osx-themes
gnome-mime-data
gnome-icon-theme
gtk-engines
tango-icon-theme

run the bluefish bundle

create a read-write image, copy Bluefish.app in there
create a symlink in the root to Applications

=== Things To do ===
* add a mime type for clojure
* remove unneeded translations

== Better MacOSX integration ==

in SVN is an initial start. The menubar is now properly integrated in the OSX menu.

what needs to be done:
* open from the Finder
* proper icon

Compiling Bluefish from source

2023-05-05T11:57:41Z

OlivierSessink: /* Fedora packages required */

= Compiling bluefish from source tarballs =

== installing the requirements ==

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 ===
<pre>
apt install automake autoconf make libtool intltool libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>
==== Debian / Ubuntu packages for the upcoming 2.2.14 release ====
<pre>
apt install automake autoconf make libtool autopoint libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>
=== Fedora packages required ===
<pre>
dnf install automake autoconf libtool gtk3-devel enchant2-devel libxml2-devel gucharmap-devel python3-devel gettext-devel
</pre>

== Getting and compiling ==
* 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 =
=== Building (assumes required packages have been installed) ===
{{SVN|checkout}}
cd bluefish-code/bluefish
./autogen.sh
./configure
make
sudo make install

=== Debian and Ubuntu packages required to build from subversion ===
<pre>
apt install libtool autopoint automake autoconf make libgtk-3-dev libenchant-2-dev libgucharmap-2-90-dev libxml2-dev subversion python3-dev
</pre>

Compiling Bluefish from source

2023-05-05T11:56:09Z

OlivierSessink: /* Fedora packages required */

= Compiling bluefish from source tarballs =

== installing the requirements ==

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 ===
<pre>
apt install automake autoconf make libtool intltool libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>
==== Debian / Ubuntu packages for the upcoming 2.2.14 release ====
<pre>
apt install automake autoconf make libtool autopoint libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>
=== Fedora packages required ===
<pre>
dnf install automake autoconf gtk3-devel enchant2-devel libxml2-devel gucharmap-devel python3-devel gettext-devel
</pre>

== Getting and compiling ==
* 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 =
=== Building (assumes required packages have been installed) ===
{{SVN|checkout}}
cd bluefish-code/bluefish
./autogen.sh
./configure
make
sudo make install

=== Debian and Ubuntu packages required to build from subversion ===
<pre>
apt install libtool autopoint automake autoconf make libgtk-3-dev libenchant-2-dev libgucharmap-2-90-dev libxml2-dev subversion python3-dev
</pre>

Compiling Bluefish from source

2023-05-05T11:55:55Z

OlivierSessink: /* installing the requirements */

= Compiling bluefish from source tarballs =

== installing the requirements ==

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 ===
<pre>
apt install automake autoconf make libtool intltool libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>
==== Debian / Ubuntu packages for the upcoming 2.2.14 release ====
<pre>
apt install automake autoconf make libtool autopoint libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>
=== Fedora packages required ===
dnf install automake autoconf gtk3-devel enchant2-devel libxml2-devel gucharmap-devel python3-devel gettext-devel

== Getting and compiling ==
* 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 =
=== Building (assumes required packages have been installed) ===
{{SVN|checkout}}
cd bluefish-code/bluefish
./autogen.sh
./configure
make
sudo make install

=== Debian and Ubuntu packages required to build from subversion ===
<pre>
apt install libtool autopoint automake autoconf make libgtk-3-dev libenchant-2-dev libgucharmap-2-90-dev libxml2-dev subversion python3-dev
</pre>

Compiling Bluefish from source

2023-05-05T11:50:04Z

OlivierSessink: /* Debian and Ubuntu packages required */

= Compiling bluefish from source tarballs =

== installing the requirements ==

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 ===
<pre>
apt install automake autoconf make libtool intltool libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>

=== for the upcoming 2.2.14 release the following packages are required ===
<pre>
apt install automake autoconf make libtool autopoint libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>

== Getting and compiling ==
* 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 =
=== Building (assumes required packages have been installed) ===
{{SVN|checkout}}
cd bluefish-code/bluefish
./autogen.sh
./configure
make
sudo make install

=== Debian and Ubuntu packages required to build from subversion ===
<pre>
apt install libtool autopoint automake autoconf make libgtk-3-dev libenchant-2-dev libgucharmap-2-90-dev libxml2-dev subversion python3-dev
</pre>

Compiling Bluefish from source

2023-05-05T11:49:21Z

OlivierSessink: /* Debian and Ubuntu packages required to build from subversion */

= Compiling bluefish from source tarballs =

== installing the requirements ==

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 ===
* automake
* autoconf
* make
* libtool
* intltool
* libgtk-3-dev
* libxml2-dev
and optional
* libenchant-dev
* libgucharmap-2-90-dev
* python-dev
=== for the upcoming 2.2.14 release the following packages are required ===
<pre>
apt install automake autoconf make libtool autopoint libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>

== Getting and compiling ==
* 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 =
=== Building (assumes required packages have been installed) ===
{{SVN|checkout}}
cd bluefish-code/bluefish
./autogen.sh
./configure
make
sudo make install

=== Debian and Ubuntu packages required to build from subversion ===
<pre>
apt install libtool autopoint automake autoconf make libgtk-3-dev libenchant-2-dev libgucharmap-2-90-dev libxml2-dev subversion python3-dev
</pre>

Compiling Bluefish from source

2023-05-05T11:48:29Z

OlivierSessink: /* for the upcoming 2.2.14 release the following packages are required */

= Compiling bluefish from source tarballs =

== installing the requirements ==

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 ===
* automake
* autoconf
* make
* libtool
* intltool
* libgtk-3-dev
* libxml2-dev
and optional
* libenchant-dev
* libgucharmap-2-90-dev
* python-dev
=== for the upcoming 2.2.14 release the following packages are required ===
<pre>
apt install automake autoconf make libtool autopoint libgtk-3-dev libxml2-dev libenchant-2-dev libgucharmap-2-90-dev python3-dev
</pre>

== Getting and compiling ==
* 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 =
=== Building (assumes required packages have been installed) ===
{{SVN|checkout}}
cd bluefish-code/bluefish
./autogen.sh
./configure
make
sudo make install

=== Debian and Ubuntu packages required to build from subversion ===
* libtool
* intltool
* automake
* autoconf
* make
* libgtk-3-dev
* libenchant-dev
* libgucharmap-2-90-dev
* libxml2-dev
* subversion
* python-dev