Code::Blocks - User contributions [en]

FAQ

2005-04-06T14:10:07Z

62.103.55.114: Note about dev-cpp auto-detection

(Stolderized from [https://www.codeblocks.org/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=1 here])

= General =

== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==

Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)

== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==

Since version 1.0-beta5, no it is not. Code::Blocks works with GNU "make" [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to "Project/Build options", switch to the "Other" tab and select the build method you prefer.

== What licence is Code::Blocks released under? ==

GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])

= Compiling =

== What compiler can I use with Code::Blocks? ==

Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.

As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.

== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==

''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''

You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under "Settings/Configure plugins/Compiler" in the "Programs" tab...
Second, you have to add two additional compiler (include) dirs. Go to "Settings/Configure plugins/Compiler" and in the "Compiler dirs" tab add "dev-cpp\include\c++" and "dev-cpp\include\c++\mingw32" (substituting "dev-cpp" with the actual dev-cpp installation folder).

== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==

BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.

== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==

Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a "Custom Makefile" checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.
Also make sure that "GNU make" is the selected build method for the specific compiler.

== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==

Click on "Project/Build options" and select the compiler you want for your project/target.

FAQ

2005-03-15T11:41:25Z

62.103.55.114: Initial (author: me22?)

(Stolderized from [https://www.codeblocks.org/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=1 here])

= General =

== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==

Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)

== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==

Since version 1.0-beta5, no it is not. Code::Blocks works with GNU "make" [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to "Project/Build options", switch to the "Other" tab and select the build method you prefer.

== What licence is Code::Blocks released under? ==

GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])

= Compiling =

== What compiler can I use with Code::Blocks? ==

Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.

As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003 and Borland's C++ Compiler 5.5

== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==

You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under "Settings/Configure plugins/Compiler" in the "Programs" tab...
Second, you have to add two additional compiler (include) dirs. Go to "Settings/Configure plugins/Compiler" and in the "Compiler dirs" tab add "dev-cpp\include\c++" and "dev-cpp\include\c++\mingw32" (substituting "dev-cpp" with the actual dev-cpp installation folder).

== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==

BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.

== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==

Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a "Custom Makefile" checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.
Also make sure that "GNU make" is the selected build method for the specific compiler.

== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==

Click on "Project/Build options" and select the compiler you want for your project/target.

Installing Code::Blocks from source on Gentoo

2005-03-15T11:40:24Z

62.103.55.114: Initial (author: me22)

'''WORK IN PROGRESS'''

( Note: This is non-official and unverified. It worked for me, but... )

===Prepare Libraries===

Code::Blocks uses the [http://www.wxwindows.org/ wxWidgets] library for its GUI. wxWidgets is turn uses [http://www.gtk.org/ GTK+]. GTK+ is the library the GNOME desktop uses, but GNOME is not required to use it. In fact, odds are very good that if you have a number of GUI programs installed, you already have it. wxWidgets is also very common, if slightly less so. The trick with wxWidgets and Code::Blocks is that Code::Blocks can only use the gtk2, non-unicode version of wxWidgets

This means that you need to compile the wxGTK package with the following use flags settings:
+no_wxgtk1 +gtk2 -unicode
The best way of getting these set is by adding a line to /etc/portage/package.use and recompiling wxGTK :
# echo x11-libs/wxGTK no_wxgtk1 gtk2 -unicode >> /etc/portage/package.use
# emerge wxGTK

===Get the source code===

For this you have 2 options:

====Option 1: Download a source tarball.====

This is easy and means you have an easily-reproduced source set.

1) '''Download a source tarball''' from [https://www.codeblocks.org/modules.php?op=modload&name=Downloads&file=index&req=viewsdownload&sid=3 The Download Section of CodeBlocks.org]

2) '''Extract it'''. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however. This should create a CodeBlocks-1.0-beta5 ( or similar ) folder.

====Option 2: Fetch from CVS====

This is not signifigantly harder and means you have a more up-to-date version of the source code. Usually this means more features and different bugs, which might be more or less annoying.

1) '''Install the CVS client'''. You might have it already. If not, this just requires the usual :
# emerge dev-util/cvs

2) '''Set the CVS root'''. Run the following command, and enter the password ''anonymous'' when asked :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login

3) '''Checkout a copy'''. cd to the directory you want the code to be placed in. Note that CVS will create a codeblocks directory for you. For this tutorial, I'm going to assume that you're installing as root, so /usr/local/src is a good pick. Any location is fine, however.
# cd /usr/local/src
The following command fetches the source from the CVS server :
# cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks checkout codeblocks

===Compile the Code===

1) '''cd to the directory with the Makefile'''. From CVS this will be <?>; from a tarball, <?> :
# cd <?>
or
# cd <?>

2) '''Build the sources'''. There's no configuration nessesary, just let make go to work :
# make -f Makefile.unix

===More===

to come

===References===

[https://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&t=29 Linux releases or compiling on Linux] from the forum

[http://sourceforge.net/cvs/?group_id=126998 Code::Blocks : CVS access instructions]

[http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS Services]

===Credits===

Original Author: me22 ( me22.ca@gmail.com ) For some reason this Wiki is spazzing when I try and use a non-anonymous account.

Installing a supported compiler

2005-03-15T11:39:10Z

62.103.55.114: Initial

Currently supported compilers, at the time of this writing are:
* [http://gcc.gnu.org/ GNU GCC] (Linux)
* [http://www.mingw.org MinGW GCC] (Win32)
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003] (Win32)
* [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars] (Win32)

When you launch Code::Blocks for the first time, it will scan the system for any supported compilers (it takes virtually no time). After this scan completes, Code::Blocks will have been configured for the found compiler(s). Code::Blocks will also be configured even for compilers that were not found (default installation settings will be used for each of those compilers).

For more info on how to download and install each of the above compilers, please read on.

=== Downloading the GNU GCC compiler & GDB debugger ===

Go to MinGW's [http://www.mingw.org/download.shtml downloads] page and download the file named <code>MinGW-x.y.z.exe</code>, where x, y and z are version numbers. At the time of this writing, this file is <code>MinGW-3.1.0-1.exe</code>. If you consider yourself lucky, you might also try <code>MinGW-3.2.0-rc-3.exe</code>. It's not a stable release yet, but it works and lacks some bugs the older version has.
These setup files contain everything needed to compile and debug windows programs.

=== Downloading the Microsoft Visual C++ Free Toolkit 2003 ===

Go to this [http://msdn.microsoft.com/visualc/vctoolkit2003 MSDN site] and click on the link labeled "Download the Visual C++ Toolkit 2003". This will download the setup file.

NOTE: ''This download is <u>not sufficient</u> for building windows programs. You will also have to download and install the [http://www.microsoft.com/msdownload/platformsdk/instmsi.htm Microsoft Platform SDK]''...

=== Downloading the Borland C++ Compiler 5.5 ===

NOTE: ''At some point, you will be asked to register with Borland and fill out a survey. Registration is free.''

Go to [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's downloads] and click on the link labeled "Compiler". After you accept the license agreement, you will be provided with download links to the setup file.

=== Downloading the Digital Mars Free Compiler ===

NOTE: ''Code::Blocks support for DigitalMars was added in 1.0-beta6.''

Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you 'll be redirected to a page containing download links. Download the compiler (current version is 8.41). You might also want to download the resource compiler (in basic utilities), as well as the STLport.

=== Compiler-neutral setup steps ===

Now that you have downloaded the setup file of the compiler of your choice, launch its installation by double-clicking on the setup file. The actual installation process is really simple. Just press "Next" all the way and you 're done.

If you installed the compiler on its default installation directory, there is nothing more to configure. Launch Code::Blocks and you 're all set :)

If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
If your compiler was not auto-detected, go to "Settings/Configure plugins/Compiler", select the compiler you installed, switch to the "Programs" page and press "Auto-detect".
If you get a message saying that the compiler was auto-detected, congratulations!
If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''

Installing Code::Blocks

2005-03-15T11:38:18Z

62.103.55.114: Initial

== Code::Blocks installation procedure under Windows ==

The first step is to download the Code::Blocks setup file from [https://www.codeblocks.org/modules.php?op=modload&name=Downloads&file=index&req=viewdownload&cid=1 here].

After you download the setup file you selected, launch it to start the setup process. The setup program is a standard installer for Windows. Just press "Next" after reading each screen. You will be given the chance to read the program license, enter the installation directory and select which plugins you want installed.
A help text on installing a compiler will also appear. Read it!

'''''Note:'''''
''Most other IDEs, behave strangely when installed in a directory whose path contains spaces. Code::Blocks IDE '''does not''' suffer from this problem! Feel free to install it in whichever path you like!''

'''''Note 2:'''''
''If you 'll be using MinGW GCC with Code::Blocks, two MinGW programs <u>do have problems</u> with spaces in filenames: <code>windres.exe</code> (resource compiler) and <code>gdb.exe</code> (GNU debugger). If you plan on using any of these two programs, avoid placing your projects in paths containing spaces.''

Main Page

2005-03-15T11:35:05Z

62.103.55.114: Initial welcome message

= Welcome to the official wiki site for Code::Blocks =
[https://www.codeblocks.org Code::Blocks] is an open-source, cross-platform IDE (Integrated Development Environment). Using a plugin architecture, it's capabilities and features are defined by the provided plugins. Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++. At the time of this writing, four (4) major C/C++ compilers are supported:
* [http://gcc.gnu.org/ GNU GCC] (Linux)
* [http://www.mingw.org MinGW GCC] (Win32)
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003] (Win32)
* [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars] (Win32)

This site does not hold much information yet but, with the help of the [https://www.codeblocks.org Code::Blocks] users, we hope it will soon be filled with articles, tutorials, FAQs, etc.

== Table of contents ==
* [[Articles]]
* [[Tutorials]]
* [[FAQ]]
* [[Tips'n'Tricks]]

The [https://www.codeblocks.org Code::Blocks] Team.