Installing Code::Blocks from source on Linux - Revision history

MortenMacFly: Spelling

2023-07-08T05:20:53Z

Spelling

LETARTARE: /* Checking the presence of GTK+ library */

2017-10-18T16:31:39Z

Checking the presence of GTK+ library

Stahta01: /* Added example update-alternatives --install */

2015-02-23T01:03:06Z

Added example update-alternatives --install

MortenMacFly: /* Resolving runtime issues */

2012-05-05T08:12:40Z

Resolving runtime issues

MortenMacFly: /* Installing Code::Blocks sources */

2012-05-05T07:59:24Z

Installing Code::Blocks sources

MortenMacFly: /* Installing Code::Blocks sources */

2012-05-05T07:59:03Z

Installing Code::Blocks sources

MortenMacFly: /* Resolving issues */

2012-05-05T07:57:28Z

Resolving issues

MortenMacFly: /* From SVN repository */

2012-05-05T07:57:07Z

From SVN repository

MortenMacFly: /* From SVN repository */

2012-05-05T07:55:59Z

From SVN repository

MortenMacFly: /* From SVN repository */

2012-05-05T07:47:44Z

From SVN repository

@@ Line 9: / Line 9: @@
 A possible implementation which does not exist:
-''Code::Blocks  ->  xwWidget (libwxX11)  ->  X''
+''Code::Blocks  ->  wxWidgets (libwxX11)  ->  X''
 Current Code::Blocks implementation:
-''Code::Blocks  ->  '''xwWidget (> libwxGTK2.8)'''  ->  '''GTK+ (> libgtk-x11-2.0)'''  ->  X''
+''Code::Blocks  ->  '''wxWidgets (> libwxGTK2.8)'''  ->  '''GTK+ (> libgtk-x11-2.0)'''  ->  X''
 This document helps you to install libwxGTK if necessary but does not cover the installation of GTK+. GTK+ is probably installed on your Linux anyway, so don't worry ;)

@@ Line 25: / Line 25: @@
 === Checking the presence of GTK+ library ===
-Have a look in /usr/lib for something like "libgtk-x11-2.0.so" (Note the library must be 2.0 minimum). Alternatively, do a search with your package manager or go to your Linux distribution forum for help. If you don't want to loose time, you can even forget this check since there is a good probability that everything is already installed.
+Have a look in /usr/lib ( /usr/lib/x86_64-linux-gnu for 64 bits) for something like "libgtk-x11-2.0.so" (Note the library must be 2.0 minimum). Alternatively, do a search with your package manager or go to your Linux distribution forum for help. If you don't want to loose time, you can even forget this check since there is a good probability that everything is already installed.
 ===Library wxGTK installation===

← Older revision		Revision as of 01:03, 23 February 2015
Line 47:		Line 47:

	to see which version of libwx is there or not and currently active.		to see which version of libwx is there or not and currently active.
		+
		+	And, Debian and Ubuntu user can use this to add a value to the list of choices
		+
		+	<pre>$ update-alternatives --install /usr/bin/wx-config wx-config /opt/wx/2.8/bin/wx-config 50</pre>

	====Getting wxGTK sources====		====Getting wxGTK sources====

← Older revision		Revision as of 08:12, 5 May 2012
Line 212:		Line 212:
	ldconfig		ldconfig
	That's it - Code::Blocks should now work just fine as all libraries are being found.		That's it - Code::Blocks should now work just fine as all libraries are being found.
		+
		+	Note that for both you may need super user rights again - so use the sudo command as needed.

@@ Line 167: / Line 167: @@
   make install</pre>
-You may need to run make install with super suer rights, in that case use:
+You may need to run make install with super user rights, in that case use:
 <pre> sudo make install</pre>
 ...for the last step.

@@ Line 163: / Line 163: @@
 ====Installing Code::Blocks sources====
 You can read the BUILD file included in the source, but everything is very straightforward. Do:
 <pre> ./configure
   make
   make install</pre>
 If you have multiple versions of wxWidgets installed or kept them in place, you can use:

@@ Line 199: / Line 199: @@
 <pre> ./configure --with-wx-config=wx-config-2.8</pre>
-====Resolving issues====
+====Resolving runtime issues====
 When running Code::Blocks after the installation it might happen, that the system complains:

@@ Line 117: / Line 117: @@
 If you are a ''Gentoo'' user at this point, please see [[Compiling_Code::Blocks_in_Gentoo]].
-Before beginning, it is often a good idea to check you have recent versions of autoconf and automake - repositories versions are not always recent enough. (if you do not have automake, then you will get "cannot find aclocal" error). If you're compiling the svn trunk versions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks. In short, these commands build Code::Blocks from sources:
+Before beginning, it is often a good idea to check you have recent versions of autoconf and automake - repositories versions are not always recent enough. (if you do not have automake, then you will get "cannot find aclocal" error). If you're compiling the svn trunk versions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks. In short, these commands build Code::Blocks from sources ''and'' installs it:
 <pre> ./bootstrap
   ./configure

@@ Line 117: / Line 117: @@
 If you are a ''Gentoo'' user at this point, please see [[Compiling_Code::Blocks_in_Gentoo]].
-Before beginning, it is often a good idea to check you have recent versions of autoconf and automake - repositories versions are not always recent enough. (if you do not have automake, then you will get "cannot find aclocal" error). If you're compiling the svn trunk versions of CodeBlocks (or future versions) then the unix build has switched to autotools.  So first build wxWidgets as described above and then build CodeBlocks as follows:
+Before beginning, it is often a good idea to check you have recent versions of autoconf and automake - repositories versions are not always recent enough. (if you do not have automake, then you will get "cannot find aclocal" error). If you're compiling the svn trunk versions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks. In short, these commands build Code::Blocks from sources:
 <pre> ./bootstrap</pre>
-This sets up the configure script and its dependencies.  It only needs to be run once (after downloading the source from svn).
+This sets up the configure script and its dependencies. It only needs to be run once (after downloading the source from svn).
 '''If you get errors like (...):'''
@@ Line 150: / Line 156: @@
 '''''Note for Ubuntu users:''''' The above is not the correct way to fix the AM_* errors. Rather, you only need to install the package named "wx-common" (Universe repository).
   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
+...then this can be solved by something like:
   ACLOCAL_FLAGS="-I /usr/share/aclocal" ./bootstrap
 ====Installing Code::Blocks sources====

@@ Line 125: / Line 125: @@
 '''If you get errors like (...):'''
   ./bootstrap: libtoolize: not found
-Then install the "libtool" package using your package manager.
+...then install the "libtool" package using your package manager.
   ./bootstrap: 64: ./bootstrap: aclocal: not found
-Then the "autoconf" and "automake" package using your package manager.
+...then the "autoconf" and "automake" package using your package manager.
   aclocal:configure.in:61: warning: macro `AM_OPTIONS_WXCONFIG' not found in library
-Then aclocal is having trouble finding the wxWidgets .m4 files.  You can do one of two things:
+...then aclocal is having trouble finding the wxWidgets .m4 files.  You can do one of two things:
 To just get bootstrap to find the path this time do:
 <pre>export ACLOCAL_FLAGS="-I `wx-config --prefix`/share/aclocal"</pre> <!--[[User:Jabber|Jabber]] 06:24, 2 August 2006 (EDT)-->
 To change the aclocal search path more permanently do:
   echo `wx-config --prefix`/share/aclocal >> /usr/share/aclocal/dirlist
-Then aclocal will also search somewhere like /opt/wx/2.6/share/aclocal
+Then aclocal will also search somewhere like /opt/wx/2.8/share/aclocal
 '''''Note for Ubuntu users:''''' The above is not the correct way to fix the AM_* errors. Rather, you only need to install the package named "wx-common" (Universe repository).
@@ Line 153: / Line 157: @@
   ACLOCAL_FLAGS="-I /usr/share/aclocal" ./bootstrap
 ====Installing Code::Blocks sources====