Code::Blocks - User contributions [en]

Installing Code::Blocks nightly build on Fedora

2006-09-13T19:55:23Z

Alturin:

This is a stub, help Code::Blocks by expanding this article! 
 
Basicly installation on FC5 should be something along the lines: 
 
First, find the package name: 
yum list '*code*' 
yum list '*blocks' 
su - 
<password> 
yum install $codeblocks 
 
You will need to have the 'extra' repository enabled. 

TODO: 
* Replace $codeblocks with the actual package name (remove the 'yum list' lines) 
* Explain how to enable "extra's" if they don't have it on already. 
* Maybe add a howto using yumex?

Installing Code::Blocks nightly build on Fedora

2006-09-13T19:52:38Z

Alturin:

This is a stub, help Code::Blocks by expanding this article!

Basicly installation on FC5 should be something along the lines:

First, find the package name:
yum list '*code*'
yum list '*blocks'
su -
<password>
yum install $codeblocks

You will need to have the 'extra' repository enabled.

TODO:
* Replace $codeblocks with the actual package name (remove the 'yum list' lines)
* Explain how to enable "extra's" if they don't have it on already.
* Maybe add a howto using yumex?

Installing Code::Blocks

2006-09-13T19:47:14Z

Alturin: Added placeholder to FC5 help page

[[Category:Installing Code::Blocks]]

== MS Windows ==

* [[Installing the latest official version of Code::Blocks on Windows]]
* [[Installing Code::Blocks nightly build on Windows]]
* [[Installing Code::Blocks from source on Windows]]

== Linux ==

* [[Installing Code::Blocks from source on Linux]] (applies to all distros)

=== Ubuntu ===

:* [[Installing Code::Blocks nightly build on Ubuntu]]

=== Fedora Cora 5===

:* [[Installing Code::Blocks nightly build on Fedora Core 5]]

=== RPM based distributions ===

:* [[Installing Code::Blocks from source on RPM based distributions]]

== FreeBSD ==

* [[Installing Code::Blocks from source on FreeBSD]]

== Mac OS X ==

* [[Installing Code::Blocks nightly build on Mac OS X]]

* [[Installing Code::Blocks from source on Mac OS X]]

Talk:Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2006-07-24T18:40:31Z

Alturin:

The link to the download is dead (Microsoft removed MVT 2003, now that it got replaced by the 2005 version) perhaps someone could change the link?
--[[User:Alturin|Alturin]] 14:40, 24 July 2006 (EDT)

Integrating Microsoft Visual C 6 with Code::Blocks IDE

2006-07-24T14:16:29Z

Alturin: Custom commandline

[[Category:User Documentation]]
== Attaching the compiler framework ==
You are still using Microsoft Visual C++ version 6 (MSVC6) and want to shift to Code::Blocks? Here are the steps to integrate the (commercial!) Microsoft Visual C++ version 6 compiler into Code::Blocks.

The following steps are required:

# Make a copy of the Microsoft Visual C++ Toolkit 2003 as follows:
#* Goto menu "Settings" -> "Compiler and debugger"
#* Select the "Microsoft Visual C++ Toolkit 2003", click the "Copy" Button
#* Save the copy e.g. under "Microsoft Visual C++ 6"
# Setup the compiler as follows:
#* The path setup (tab "Programs") should be done as following:
#** The "Compiler's installation directory" should be set to {YOUR_MSVC6}\VC98
#** Under "Additional path's" add:
#*** {YOUR_MSVC6_COMMON}\MSDEV98\Bin
#*** {YOUR_MSVC6_COMMON}\Tools
#* The compiler/linker setup (tab "Directories) should be done as following:
#** Under the tab "Compiler" add the following path's:
#*** {YOUR_MSVC6}\VC98\Include
#*** {YOUR_MSVC6}\VC98\MFC\Include
#*** {YOUR_MSVC6}\VC98\ATL\Include
#** Under the tab "Linker" add the following path's:
#*** {YOUR_MSVC6}\VC98\Lib
#*** {YOUR_MSVC6}\VC98\MFC\Lib
#** Under the tab "Resource compiler" add the following path's:
#*** {YOUR_MSVC6}\VC98\Include
#*** {YOUR_MSVC6}\VC98\MFC\Include
#*** {YOUR_MSVC6}\VC98\ATL\Include

That's it.

== Working with "legacy" MSVC6 workspaces/projects ==

Code::Blocks offers the ability to import Visual C++ 6 workspaces and projects. To import a MSVC6 workspace do the following: Menu "Project" -> "Import" -> "MS Visual C++ workspace". Code::Blocks will ask you if it should apply the default compiler or ask for each project which compiler to chose. Choose the second option. Now Code::Blocks will present a compiler selection dialog for each project of the workspace. Choose your newly created compiler ("Microsoft Visual C++ 6") for each project. Usually this should import your workspace just fine.

Now there is some finetuning required:

# Code::Blocks may have imported the include path's for compiler and linker as absolute path's. This you should verify and setup to relative apth's where apropriate.
# Code::Blocks may have imported the libraries to link against with absolute path's. This you should change to just present the libraries name (e.g. just "MyLib" for the "D:\MyPath\MyOtherPath\MyLib.lib" library). For own libraries there maybe an additional linker include path to be setup for the compiler to find this library.
# Code::Blocks usually does not import the "common" MSVC6 libraries you need to link your project against. Thus you will receive linker erros for unresolved symbols. The MSDN will help you to tell which of the "common" library you need to link against. For example: If the linker issues an "unresolved symbol RegCloseKey" a look in the MSDN will reveal that this is part of the "advapi32.lib". Thus just add "advapi32" (without the lib extension) to the libraries to link your project against. This may take a while but if you just start from the first unresolved symbol linking another common library will usually resolve a whole list of unresolved symbols.

== Troubleshooting ==
# For troubleshooting enable the "Full command line" Under menu "Settings" -> "Compiler" -> "Other" tab, "Compiler logging".
# If you get heaps of warnings, even when compiling a simple Hello World application, you might want to try this. (The error "unrecognized commandline option -g, ignored" should be a hint)
#* Goto menu "Settings" -> "Compiler and debugger"
#* Goto the "Other" tab
#* Hit the "Advanced Options..." button
#* Click OK (you might want to tick the "don't bug me" box)
#* Click the "Compile single file to object file" thingy (if it's not already selected), and, under "Command line macro", replace "$options" with "/nologo /W3 /GX /D "Win32".
#** /GX will fix all the warnings
#** /D "WIN32" will fix your problems if you have a large codebase, with dozens of "#ifdef WIN32" and the like.
#** /W3 you could change ofcourse, to /W1 till /W5, that's all up to you
#** /nologo I'm not sure about, I've copied most of this from the commandline MSVC++ 6.0 itself generates.

Main Page

2006-07-05T21:58:41Z

Alturin: Toolkit was removed.

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is an open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|

{{Layout_box3|1=
=== Downloading and Installing ===
* [[:Category:Installation\Build_Instructions|Installation\Build Instructions]]
* [[Installing Code::Blocks]] - Beginners start here
* [[Building From Source]] - For those experienced with C++ development
* [[Nightly Cookbook]] - How to create a nightly build (Win32)
}}

{{Layout_box2|1=
=== Using Code::Blocks ===
* [[:Category:Code::Blocks_Documentation|Documentation]]
[[Image:Chk.png]][[Scripting Code::Blocks]]
* [[:Category:Application_Development|Application Development]]
* [[Code::Blocks Interface]]
* [[FAQ]] - Frequently Asked Questions
* [[Tips'n'Tricks]]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003] (Win32) (Toolkit was removed from the msdn site)
* [http://www.borland.com/products/downloads/download_cbuilder.html Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars] (Win32)
* [http://store.scitechsoft.com/product_info.php?products_id=37/ OpenWatcom] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/219754.htm Intel C++ compiler] (Win32)
}}
|width="40%" valign="top"|

{{Layout_box4|1=
=== Downloads ===
* [/index.php?board=20.0 Nightly builds] (updated each night)
* Last official release: [https://www.codeblocks.org/downloads.shtml 1.0rc2]
}}
{{Layout_box2|1=
=== User resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [https://wiki.codeblocks.org Official wiki (this one!)]
}}
{{Layout_box2|1=
=== Developer resources ===
[[Image:Chk.png]][[Roadmap]]
* [[Developing for Code::Blocks]]
* [[Announcement for plugins/patches]] or similar
* [http://developer.berlios.de/projects/codeblocks/ Project page at BerliOS]
* '''Bugs''': [http://developer.berlios.de/bugs/?group_id=5358 Browse] or [http://developer.berlios.de/bugs/?func=addbug&group_id=5358 submit new]
* '''Features''': [http://developer.berlios.de/feature/?group_id=5358 Browse] or [http://developer.berlios.de/feature/?func=addfeature&group_id=5358 submit new]
* '''Patches''': [http://developer.berlios.de/patch/?group_id=5358 Browse] or [http://developer.berlios.de/patch/?func=addpatch&group_id=5358 submit new]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

Installing a supported compiler

2006-07-05T21:54:38Z

Alturin: Toolkit was removed.

[[Category:Installation\Build Instructions]]
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.

==Windows==
Currently supported compilers, at the time of this writing are:
* [http://www.mingw.org MinGW GCC C/C++ Free Compiler, including G77 (Fortran)]
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003]
* [http://www.borland.com/products/downloads/download_cbuilder.html Borland's C/C++ Free Compiler 5.5]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://store.scitechsoft.com/product_info.php?products_id=37/ OpenWatcom Free C/C++ Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]

=== 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 ===

====This no longer works as discribed since the Toolkit was removed in favor of the 2005 release.====

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 not sufficient 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 C/C++ Free Compiler ===

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.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

=== Configuring CodeBlocks to use the Intel C++ Compiler ===
''Note: this info is for 1.0RC1 and previous versions, now C::B haves direct support for Intel C++.''

After various user requests, we decided to post here the info to support the Intel Compiler on CodeBlocks. This should be easy, since the Intel Compiler can emulate the MSVC++ compiler.

* change MS Toolkit linker from cl.exe to icl.exe
* add (installation path to the Intel C++)\Ia32\Bin to the "Programs -> Extra paths"
* add "-D_USE_INTEL_COMPILER" to "Compiler options"
* add (installation path to the Intel C++)\Ia32\Include and \lib to the "Global compiler options -> Directories"
* add some options like "/QaxK" to the "Compiler options" (icl -help)

==Linux==
Currently supported compilers, at the time of this writing are:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]

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

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

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

Under Mac you'll need to install Xcode Tools from http://developer.apple.com/tools/

This will install Apple versions of:

http://www.gnu.org/software/gcc/
http://www.gnu.org/software/gdb/
http://www.gnu.org/software/make/

== 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.''