Bluefish Wiki:Installing Bluefish from Source - Revision history

DrMartinus: Replaced SVN-checkout with the template call

2022-12-17T12:13:37Z

Replaced SVN-checkout with the template call

← Older revision		Revision as of 12:13, 17 December 2022
Line 35:		Line 35:
	You can get the latest Bluefish version via SVN using the instructions in [[Man 2 ch01s04\|Section 4, “Latest Developmental Version”]]:		You can get the latest Bluefish version via SVN using the instructions in [[Man 2 ch01s04\|Section 4, “Latest Developmental Version”]]:
	cd TheChosenDirectory		cd TheChosenDirectory
	~~svn~~ checkout ~~https://svn.code.sf.net/p/bluefish/code/trunk bluefish-code~~		{{SVN\|checkout}}

	Next, install it with the following steps:		Next, install it with the following steps:

DrMartinus: DrMartinus moved page Bluefish Wiki:Man 2 ch02s04 to Bluefish Wiki:Installing Bluefish from Source: The former name was for navigation purpose. The navigation can be provided also in this way. In case the position needs to be changed, the name would also need to be changed. That's not the case if the name describes the contents.

2022-12-17T11:29:04Z

DrMartinus moved page Bluefish Wiki:Man 2 ch02s04 to Bluefish Wiki:Installing Bluefish from Source: The former name was for navigation purpose. The navigation can be provided also in this way. In case the position needs to be changed, the name would also need to be changed. That's not the case if the name describes the contents.

← Older revision	Revision as of 11:29, 17 December 2022
(No difference)

DrMartinus: DrMartinus moved page Man 1 ch02s04 to Bluefish Wiki:Man 2 ch02s04: Contents have been updated to be applicable to version 2

2022-12-16T15:32:09Z

DrMartinus moved page Man 1 ch02s04 to Bluefish Wiki:Man 2 ch02s04: Contents have been updated to be applicable to version 2

← Older revision	Revision as of 15:32, 16 December 2022
(No difference)

DrMartinus at 15:29, 16 December 2022

2022-12-16T15:29:30Z

← Older revision		Revision as of 15:29, 16 December 2022
Line 8:		Line 8:
	\|next=Man 2 ch02s05		\|next=Man 2 ch02s05
	}}		}}
	== Installing Bluefish from the source code ==		=== Installing Bluefish from the source code ===
	<div style="float:right; background-color:#E5ECF9;border:1px solid #3061C2;">		<div style="float:right; background-color:#E5ECF9;border:1px solid #3061C2;">
	*[[#4.1. Quick Installation Overview\| 4.1. Quick Installation Overview]]		*[[#4.1. Quick Installation Overview\| 4.1. Quick Installation Overview]]

DrMartinus: Edited the text to be applicable to version 2.2.12, rephrased some sentences and added info, where it might be helpful.

2022-12-16T15:28:16Z

Edited the text to be applicable to version 2.2.12, rephrased some sentences and added info, where it might be helpful.

← Older revision		Revision as of 15:28, 16 December 2022
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{~~Man1top~~		{{Man2top
	\|lang=en		\|lang=en
	\|rev=1.0.6		\|rev=2.2.12
	\|Title=~~4. ~~Installing a Bluefish Source Distribution		\|Title=Installing a Bluefish Source Distribution
	\|prev=Man 1 ch02s03		\|prev=Man 2 ch02s03
	\|Subtitle=Chapter II. Installing Bluefish		\|Subtitle=Chapter II. Installing Bluefish
	\|next=Man 1 ch02s05		\|next=Man 2 ch02s05
	}}		}}
	== 4. Installing a Bluefish ~~Source Distribution~~ ==		== Installing Bluefish from the source code ==
	<div style="float:right; background-color:#E5ECF9;border:1px solid #3061C2;">		<div style="float:right; background-color:#E5ECF9;border:1px solid #3061C2;">
	*[[#4.1. Quick Installation Overview\| 4.1. Quick Installation Overview]]		*[[#4.1. Quick Installation Overview\| 4.1. Quick Installation Overview]]
Line 14:		Line 14:
	*[[#4.3. Problems Compiling?\| 4.3. Problems Compiling?]]		*[[#4.3. Problems Compiling?\| 4.3. Problems Compiling?]]
	</div>		</div>
	By installing Bluefish from source, you may be able to get a newer version (from SVN) than those distributed as binaries. You may also need to compile from source if no binary is available for your system.		By installing Bluefish from source, you may be able to get a newer version (from SVN) than those distributed as binaries. You may also need to compile from source if no binary is available for your system. However, be aware that the version compiled from the newest source code may contain bugs. If you encounter any, please report them to the developers.

	=== 4.1. Quick Installation Overview ===		=== 4.1. Quick Installation Overview ===
Line 30:		Line 30:
	The '''configure''' script is used to automatically find the appropriate settings for your system. Because of differences between systems, this compile-time configuration is necessary, and configure solves this challenge easily -- with an added bonus of telling whether you have everything needed to compile.		The '''configure''' script is used to automatically find the appropriate settings for your system. Because of differences between systems, this compile-time configuration is necessary, and configure solves this challenge easily -- with an added bonus of telling whether you have everything needed to compile.

	The configure-script can be~~, um,~~ configured. This is something you most likely will not need to do, but it is easy to do if necessary. For a complete list of configure options, see [[Man 1 ch02s05\|Section 5, “Configure Options”]]		The configure-script can be configured. This is something you most likely will not need to do, but it is easy to do if necessary. For a complete list of configure options, see [[Man 2 ch02s05\|Section 5, “Configure Options”]]

	=== 4.2. Installing from Development Source Tree ===		=== 4.2. Installing from Development Source Tree ===
	You can get the latest Bluefish version via SVN using the instructions in [[Man 1 ch01s04\|Section 4, “Latest Developmental Version”]]:		You can get the latest Bluefish version via SVN using the instructions in [[Man 2 ch01s04\|Section 4, “Latest Developmental Version”]]:
	cd ~~TheChoosenDirectory~~		cd TheChosenDirectory
	svn co https://~~bluefish~~.~~svn~~.~~sourceforge~~.net/~~svnroot~~/bluefish/trunk/bluefish/		svn checkout https://svn.code.sf.net/p/bluefish/code/trunk bluefish-code

	Next, install it with the following steps:		Next, install it with the following steps:

	# Enter the directory containing the bluefish source files: <br/>'''cd ~~TheChoosenDirectory~~/bluefish'''		# Enter the directory containing the bluefish source files: <br/>'''cd TheChosenDirectory/bluefish-code'''
	# Next, generate the configure script by running <br/>'''./autogen.sh'''		# Next, generate the configure script by running <br />'''./autogen.sh'''
	# Then, you run <br/>'''./configure''' with whatever options you might want (see [[Man 1 ch02s05\|Section 5, “Configure Options”]]). <br/> This example will cause ''make install'' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr/bin/bluefish-unstable):'''./configure --prefix=/usr'''<br/>By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc.<br/>Run `./configure -h' to list available options.<br/>If configure fails, it will probably give a hint telling you what is missing or wrong.		# Then, you run <br/>'''./configure''' with whatever options you might want (see [[Man 2 ch02s05\|Section 5, “Configure Options”]]). <br/>
			This example will cause ''make install'' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr/bin/bluefish-unstable):<br />'''./configure --prefix=/usr/bin/bluefish-unstable'''<br/>By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc.<br/>Run `./configure -h' to list available options.<br/>If configure fails, it will probably give a hint telling you what is missing or wrong.
	# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run '''make'''.		# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run '''make'''.
	# When ''make'' has completed, you can install Bluefish: (''su'' to root first, unless you specified a user writable prefix to configure), then issue: '''<nowiki># make install</nowiki>'''.		# When ''make'' has completed, you can install Bluefish: (''su'' to root first, unless you specified a user writable prefix to configure), then issue: '''<nowiki># make install</nowiki>'''.
	#Now, type '''bluefish-unstable''' to run.		#Now, type '''bluefish-unstable''' to run.
	To update the sources at a later time:		To update the sources at a later time:
	# Enter the directory containing the bluefish source files: '''cd ~~TheChoosenDirectory~~/bluefish'''		# Enter the directory containing the bluefish source files: '''cd TheChosenDirectory/bluefish-code'''
	# '''svn update'''		# '''svn update'''
	# and then run '''./configure''', '''make''' and '''<nowiki>#</nowiki> make install'''.		# and then run '''./configure''', '''make''' and '''<nowiki>#</nowiki> make install'''.

	=== 4.3. Problems Compiling? ===		=== 4.3. Problems Compiling? ===
	If compilation fails, first make sure you have the necessary utilities and libraries. See [[Man 1 ch02#Section 1, “Requirements”\| Section 1, “Requirements”]].		If compilation fails, first make sure you have the necessary utilities and libraries. See [[Man 2 ch02#Section 1, “Requirements”\| Section 1, “Requirements”]].

	Next, ~~see~~ if your system is mentioned in [[Man 1 ch02s03\|Section 3, “System Specific Installation Issues”]].		Next, check if your system is mentioned in [[Man 2 ch02s03\|Section 3, “System Specific Installation Issues”]].

	Below is a list of well known problems that have been mentioned on the bluefish-dev list:		Below is a list of well known problems that have been mentioned on the bluefish-dev list:

	* make: *** No targets specified and no makefile found. Stop.<br/> This will happen if ''configure'' fails and you try to run '''make'''. It also happens if you're running '''make''' from the wrong directory.		* make: *** <tt>No targets specified and no makefile found. Stop.</tt><br/> This will happen if ''configure'' fails and you try to run '''make'''. Check the output of ''configure'' thoroughly and resolve any errors. Then run ''make''. <br />It also happens if you're running '''make''' from the wrong directory. It must be run from the same directory where the source code has been downloaded to and where ''./configure'' has been run.
	* ... more trouble to come ;-)		* ... more trouble to come ;-)

	If you're unable to find a solution (or if you think you have a solution others might want), feel free to contact us on the ''bluefish-dev'' list (See [[Man 1 pr01s02#2.4. Contact Us\| Section 2.4, “Contact Us”]]). You may want to contact the bluefish package maintainer for your distribution first when appropriated.		If you're unable to find a solution (or if you think you have a solution others might want), feel free to contact us on the ''bluefish-dev'' list (See [[Man 2 pr01s02#2.4. Contact Us\| Section 2.4, “Contact Us”]]). You may want to contact the bluefish package maintainer for your distribution first when appropriated.



	{{~~Man1bottom~~		{{Man2bottom
	\|prev=Man 1 ch02s03		\|prev=Man 1 ch02s03
	\|up=Man 1 ch02		\|up=Man 1 ch02

Fal7i: /* 4.2. Installing from Development Source Tree */

2009-09-20T08:12:10Z

4.2. Installing from Development Source Tree

← Older revision		Revision as of 08:12, 20 September 2009
Line 41:		Line 41:
	# Enter the directory containing the bluefish source files: <br/>'''cd TheChoosenDirectory/bluefish'''		# Enter the directory containing the bluefish source files: <br/>'''cd TheChoosenDirectory/bluefish'''
	# Next, generate the configure script by running <br/>'''./autogen.sh'''		# Next, generate the configure script by running <br/>'''./autogen.sh'''
	# Then, you run <br/>'''./configure''' with whatever options you might want. <br/> This example will cause ''make install'' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr/bin/bluefish-unstable):'''./configure --prefix=/usr'''<br/>By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc.<br/>Run `./configure -h' to list available options.<br/>If configure fails, it will probably give a hint telling you what is missing or wrong.		# Then, you run <br/>'''./configure''' with whatever options you might want (see [[Man 1 ch02s05\|Section 5, “Configure Options”]]). <br/> This example will cause ''make install'' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr/bin/bluefish-unstable):'''./configure --prefix=/usr'''<br/>By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc.<br/>Run `./configure -h' to list available options.<br/>If configure fails, it will probably give a hint telling you what is missing or wrong.
	# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run '''make'''.		# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run '''make'''.
	# When ''make'' has completed, you can install Bluefish: (''su'' to root first, unless you specified a user writable prefix to configure), then issue: '''<nowiki># make install</nowiki>'''.		# When ''make'' has completed, you can install Bluefish: (''su'' to root first, unless you specified a user writable prefix to configure), then issue: '''<nowiki># make install</nowiki>'''.

Fal7i: typo

2009-09-20T08:07:05Z

typo

← Older revision		Revision as of 08:07, 20 September 2009
Line 21:		Line 21:
	Bluefish is installed using the standard 'configure, make, make install' steps. Assuming you have downloaded a bluefish source package, for instance bluefish-ver.tar.gz (naturally, change the filename to what's appropriate), you complete the installation with the following steps:		Bluefish is installed using the standard 'configure, make, make install' steps. Assuming you have downloaded a bluefish source package, for instance bluefish-ver.tar.gz (naturally, change the filename to what's appropriate), you complete the installation with the following steps:

	# ~~<tt>~~'''tar -zxvf bluefish-ver.tar.gz'''~~</tt>~~		# '''tar -zxvf bluefish-ver.tar.gz'''
	# ~~<tt>~~'''cd bluefish-ver'''~~</tt>~~		# '''cd bluefish-ver'''
	# ~~<tt>~~'''./configure'''~~</tt>~~		# '''./configure''' (see [[Man 1 ch02s05\|Section 5, “Configure Options”]])
	# ~~<tt>~~'''make'''~~</tt>~~		# '''make'''
	# ~~<tt>~~'''su -c 'make install''''~~</tt>~~		# '''su -c 'make install''''
	# Now, type ~~<tt>~~'''bluefish'''~~</tt>~~ to run. You may delete the bluefish-ver directory.		# Now, type '''bluefish''' to run. You may delete the bluefish-ver directory.

	The '''configure''' script is used to automatically find the appropriate settings for your system. Because of differences between systems, this compile-time configuration is necessary, and configure solves this challenge easily -- with an added bonus of telling whether you have everything needed to compile.		The '''configure''' script is used to automatically find the appropriate settings for your system. Because of differences between systems, this compile-time configuration is necessary, and configure solves this challenge easily -- with an added bonus of telling whether you have everything needed to compile.

Fal7i: typo

2009-09-20T07:06:37Z

typo

← Older revision		Revision as of 07:06, 20 September 2009
Line 34:		Line 34:
	=== 4.2. Installing from Development Source Tree ===		=== 4.2. Installing from Development Source Tree ===
	You can get the latest Bluefish version via SVN using the instructions in [[Man 1 ch01s04\|Section 4, “Latest Developmental Version”]]:		You can get the latest Bluefish version via SVN using the instructions in [[Man 1 ch01s04\|Section 4, “Latest Developmental Version”]]:
	$ cd TheChoosenDirectory		cd TheChoosenDirectory
	$ svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/		svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/

	Next, install it with the following steps:		Next, install it with the following steps:

	# Enter the directory containing the bluefish source files: ''cd TheChoosenDirectory/bluefish''		# Enter the directory containing the bluefish source files: <br/>'''cd TheChoosenDirectory/bluefish'''
	# Next, generate the configure script by running ''./autogen.sh''		# Next, generate the configure script by running <br/>'''./autogen.sh'''
	# Then, you run ''configure'' with whatever options you might want. <br/> This example will cause ''make install'' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr/bin/bluefish).		# Then, you run <br/>'''./configure''' with whatever options you might want. <br/> This example will cause ''make install'' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr/bin/bluefish-unstable):'''./configure --prefix=/usr'''<br/>By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc.<br/>Run `./configure -h' to list available options.<br/>If configure fails, it will probably give a hint telling you what is missing or wrong.
	~~'''$~~''' ./configure --prefix=/usr		# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run '''make'''.
	By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc.		# When ''make'' has completed, you can install Bluefish: (''su'' to root first, unless you specified a user writable prefix to configure), then issue: '''<nowiki># make install</nowiki>'''.
	Run `./configure -h' to list available options.		#Now, type '''bluefish-unstable''' to run.

	If configure fails, it will probably give a hint telling you what is missing or wrong.
	# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run ~~<tt>~~'''make'''~~</tt>~~.
	# When ''make'' has completed, you can install Bluefish: (''su'' to root first, unless you specified a user writable prefix to configure), then issue: ''<nowiki># make install</nowiki>''.

	To update the sources at a later time:		To update the sources at a later time:
	* Enter the directory containing the bluefish source files: ''cd TheChoosenDirectory/bluefish''		# Enter the directory containing the bluefish source files: '''cd TheChoosenDirectory/bluefish'''
	$ svn update		# '''svn update'''
	and then ./configure, make, make install.		# and then run '''./configure''', '''make''' and '''<nowiki>#</nowiki> make install'''.

	=== 4.3. Problems Compiling? ===		=== 4.3. Problems Compiling? ===

Fal7i: /* 4.2. Installing from Development Source Tree */

2009-09-19T20:32:29Z

4.2. Installing from Development Source Tree

← Older revision		Revision as of 20:32, 19 September 2009
Line 33:		Line 33:

	=== 4.2. Installing from Development Source Tree ===		=== 4.2. Installing from Development Source Tree ===
	You can get the latest Bluefish version via SVN using the instructions in [[Man 1 ch01s04\|Section 4, “Latest Developmental Version”]]. ~~Next, install it with the following steps:~~		You can get the latest Bluefish version via SVN using the instructions in [[Man 1 ch01s04\|Section 4, “Latest Developmental Version”]]:
			$ cd TheChoosenDirectory
			$ svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/

	# Enter the directory containing the bluefish source files: ~~<tt>'~~''cd bluefish''~~'</tt>~~		Next, install it with the following steps:
	# Next, generate the configure script by running ~~<tt>'~~''./autogen.sh''~~'</tt>~~
	# Then, you run '''configure''' with whatever options you might want. <br/> This example will cause '''make install''' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr~~/local/bf-cvs~~/bin/bluefish). ~~This is most likely not what you want -- just run configure without parameters instead.<br/>~~ '''$''' ./configure --prefix=/usr/local/bf-~~cvs<br/>~~ If configure fails, it will probably give a hint telling you what is missing or wrong.		# Enter the directory containing the bluefish source files: ''cd TheChoosenDirectory/bluefish''
			# Next, generate the configure script by running ''./autogen.sh''
			# Then, you run ''configure'' with whatever options you might want. <br/> This example will cause ''make install'' to install Bluefish with the specified directory as prefix (i.e. the binary is installed in /usr/bin/bluefish).
			'''$''' ./configure --prefix=/usr
			By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc.
			Run `./configure -h' to list available options.

			If configure fails, it will probably give a hint telling you what is missing or wrong.
	# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run <tt>'''make'''</tt>.		# Assuming it completed successfully, your next step is to compile Bluefish. To do this, run <tt>'''make'''</tt>.
	# When '''make''' has completed, you can install Bluefish: ('''su''' to root first, unless you specified a user writable prefix to configure), then issue: ~~<tt>'~~''<nowiki># make install</nowiki>''~~'</tt>.~~		# When ''make'' has completed, you can install Bluefish: (''su'' to root first, unless you specified a user writable prefix to configure), then issue: ''<nowiki># make install</nowiki>''.

	~~To update the sources at a later time, you run the command:~~
	~~$ svn co https://bluefish~~.~~svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/ bluefish~~

			To update the sources at a later time:
			* Enter the directory containing the bluefish source files: ''cd TheChoosenDirectory/bluefish''
			$ svn update
			and then ./configure, make, make install.

	=== 4.3. Problems Compiling? ===		=== 4.3. Problems Compiling? ===

Fal7i at 19:53, 19 August 2009

2009-08-19T19:53:49Z

← Older revision		Revision as of 19:53, 19 August 2009
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	~~__NOEDITSECTION__~~
	{{Man1top		{{Man1top
	\|lang=en		\|lang=en
Line 42:		Line 41:
	# When '''make''' has completed, you can install Bluefish: ('''su''' to root first, unless you specified a user writable prefix to configure), then issue: <tt>'''<nowiki># make install</nowiki>'''</tt>.		# When '''make''' has completed, you can install Bluefish: ('''su''' to root first, unless you specified a user writable prefix to configure), then issue: <tt>'''<nowiki># make install</nowiki>'''</tt>.

	To update the sources at a later time, yo run the command:		To update the sources at a later time, you run the command:
	$ svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/ bluefish		$ svn co https://bluefish.svn.sourceforge.net/svnroot/bluefish/trunk/bluefish/ bluefish