- Code Blocks
- Advertisement
- Advertisement
- Downloads
- # Change Log
- Description
- Code::Blocks Review
- Downloads
- Download the binary release
- Download a nightly build
- Download the source code
- Retrieve source code from SVN
- Binary releases
- Microsoft Windows
- Linux 32 and 64-bit
- Mac OS X
- [Code::Blocks] Compile 64-bit under windows with MinGW-w64
Code Blocks
Advertisement
Advertisement
Downloads
# Change Log
This is just an excerpt of the changelog with the differences since 17.12. You can read a full changelog on the Code::Blocks homepage.
* This release introduces new icon sizes (16, 20, 24, 28, 32, 40, 48, 56 and 64) for almost every UI element (menus, toolbars, project tree, most plugins).
* The icon size is appropriately selected based on the scaling used by the user. The goal is to make icons look big enough and non-blurry. This should work correctly on all major ports (wxMSW, wxGTK, wxCocoa)
* The icons in the editor’s margin change size when scaling the editor.
* The icons in the auto-completion popup change size to match the scaling of the text.
* Code::Blocks is marked as DPI-aware:True on Windows which makes it look sharp. Per-monitor support is not yet available.
* The Scintilla component has been updated to version 3.7.5 and most of the code has been synchronized with the code for wxSTC.
* This release introduces some improvements to handling multiple selection. Now it is possible to paste when multiple selections are active.
* A major flickering bug has been fixed when using wxGTK.
* Support for fonts with ligatures on all platforms has been introduced.
* Non-latin keys now work when used as shortcuts in the editor on Linux.
* There is an option to disable the save-to-temp-and-move operation we use by default.
* The context menu has been trimmed down and organized in a better way. Some options are no longer duplicated in the editor and editor notebook context menus.
* More advanced options for closing files have been added to the editor notebook context menu (close to the right/left).
* Lexers for several new languages have been added (Markdown, Nim, Plain text, YAML).
* Small improvements to the settings of the syntax highlighting.
* Add an option to targets which allows the user to select the linker executable to be used for the target. This makes C only project to use the C compiler executable for linking.
* Clear target specific variables from the MacroManager on every recalculation (ticket #582).
* Various improvements to the logging and auto switching to the log tabs.
* Add support for -std=c++17 flag.
* Make the abort button work again (ticket #104). Kill the started process and all children instead of using wxSIGTERM.
* The C/C++ parser used by the Code-completion plugin saw various improvements and bugfixes.
* Various improvements to multi-monitor support and child window placement.
* Do View — Toolbars — Fit toolbars on every startup.
* Many wxWidgets asserts have been fixed.
* Make sure passing —file=path/to/file.ext without line number works, too.
* Make pressing Return/Enter to select the filtered option in the Goto File, Goto Function and Select Target dialogs on Windows.
* SDK: Introduce API for Memory watches which might be used to implement plugins useful for embedded development.
* SDK: Make cbResolveSymLinkedDirPath a bit more robust (prevent infinite loops).
* Improved performance when loading large projects.
* Improved performance when opening the find/replace dialog when there is a project with many targets.
* Script bindings: Make it possible to examine and modify the Extension XML nodes in the project files.
* Debugger: Make it possible to attach to a process using the command line (This commit adds —dbg-attach and —dbg-config command line options).
* Debugger: Make sure to set the SHELL variable before starting GDB
* KeyBinder: Introduce version 2.0 using CodeLight key binding methods; allowing future ability to dynamically set menu and global accelerators to any frame.
* KeyBinder: Fix F2, Shift-F2 and allow linux to handle any View menu check items (ticket #273).
* SpellChecker: Fix wrong white space handling on windows by using Scintilla word finding function.
* wxSmith: Add various missing flags to various controls.
* wxSmith: Improve the UI, fix various crashes and asserts.
* Scintilla to 3.7.5; Sync wx files with the same files in wxWidgets’ master
* Exchndl crash handler to v0.9.1
* Hunspell on Windows from v1.3.3 to v1.7.0
* wxPDFDoc to v0.9.8 (used in SourceExporter plugin)
Christophe Marc BERTONCINI
GГ©rard Durand (gd_on)
Juan Manuel FernГЎndez MuГ±oz
Description
Code Blocks is an open source, free, C, C++ and Fortran IDE cross-platform that provides a ton of options. It is a no-cost C++IDE created with for users who have high demands.
Those behind this free software program designed it for extensive user customization and maximum flexibility. Centered on a plug-in style framework, the software is capable of being extended in the user’s preferred manner. There is even a built-in plug-in wizard that empowers users to build their unique plug-ins.
IMPORTANT: We currently do not list Code::Blocks Linux versions, but you can find all of them on projects homepage here.
Code::Blocks Review
How Code::Blocks is Different From the Competition
Unlike other IDEs that are overly complex and require extensive time to figure out, Code::Blocks has a short learning curve. The masterminds behind the software created it with a solid user experience design that makes it easy for users to figure out all the software’s nuances on the fly. The software actually replicates the user experience design of Visual Studio, so many users will find that Code::Blocks is quite intuitive.
Positives
Aside from its excellent user experience design, Code::Blocks also shines in a number of other areas. Those who detest writing UI code will find that the software does most of the work. Code::Blocks does not create unorganized, faulty code in the slightest. Instead, it generates UI code into C+ files (both .cpp and .h) that users can proceed to edit as they would with normal text files as long as it is not necessary to insert code within the blocks that the program uses. The auto-generated UI code is shockingly clean.
The software also empowers users to move the code around as desired and the program will still recognize it as long as the blocks remain intact. Users will love the fact that they can save resources in the form of .XRC files. Aside from Code::Block’s ability to facilitate UI development, it can also function for C++ development on full-scale projects as well as everyday tasks. The IDE handles projects across different platforms without any significant issues. It is not necessary to make significant operating system changes, mess around with Makefiles or build entirely new systems for projects to compile. Just modify the Code::Block compiler settings, and you will be good to go.
Negatives
If you’re complaining regarding native Python support, this has been fixed: Python plugin is available here. You can find the debugger forum thread here.
Same for keyboard shortcut: the shortcut assignment is provided through a plugin named «Keybinder».
Some have complained that the debugger is limited compared to other programs. Many of these users have also noted that the debugger operates too slowly with Linux systems.
The Bottom Line
Code::Blocks might not be as powerful as Visual Studio yet it still provides elite functionality. It can be used for an array of production quality projects. Anyone who works with wxWidgets or production code will prefer this IDE over most others. The bottom line is that Code:Blocks is an excellent no-cost solution for C++ development with Linux.
Downloads
There are different ways to download and install Code::Blocks on your computer:
Download the binary release
This is the easy way for installing Code::Blocks. Download the setup file, run it on your computer and Code::Blocks will be installed, ready for you to work with it. Can’t get any easier than that!
Download a nightly build
There are also more recent so-called nightly builds available in the forums. Please note that we consider nightly builds to be stable, usually, unless stated otherwise.
Other distributions usually follow provided by the community (big “Thank you!” for that!). If you want to provide some, make sure to announce in the forums such that we can put it on the official C::B homepage.
Download the source code
If you feel comfortable building applications from source, then this is the recommend way to download Code::Blocks. Downloading the source code and building it yourself puts you in great control and also makes it easier for you to update to newer versions or, even better, create patches for bugs you may find and contributing them back to the community so everyone benefits.
Retrieve source code from SVN
This option is the most flexible of all but requires a little bit more work to setup. It gives you that much more flexibility though because you get access to any bug-fixing we do at the time we do it. No need to wait for the next stable release to benefit from bug-fixes!
Besides Code::Blocks itself, you can compile extra plugins from contributors to extend its functionality.
Thank you for your interest in downloading Code::Blocks!
Binary releases
Please select a setup package depending on your platform:
NOTE: For older OS’es use older releases. There are releases for many OS version and platforms on the Sourceforge.net page.
NOTE: There are also more recent nightly builds available in the forums or (for Ubuntu users) in the Ubuntu PPA repository. Please note that we consider nightly builds to be stable, usually.
NOTE: We have a Changelog for 20.03, that gives you an overview over the enhancements and fixes we have put in the new release.
NOTE: The default builds are 64 bit (starting with release 20.03). We also provide 32bit builds for convenience.
Microsoft Windows
File | Download from |
---|---|
codeblocks-20.03-setup.exe | FossHUB or Sourceforge.net |
codeblocks-20.03-setup-nonadmin.exe | FossHUB or Sourceforge.net |
codeblocks-20.03-nosetup.zip | FossHUB or Sourceforge.net |
codeblocks-20.03mingw-setup.exe | FossHUB or Sourceforge.net |
codeblocks-20.03mingw-nosetup.zip | FossHUB or Sourceforge.net |
codeblocks-20.03-32bit-setup.exe | FossHUB or Sourceforge.net |
codeblocks-20.03-32bit-setup-nonadmin.exe | FossHUB or Sourceforge.net |
codeblocks-20.03-32bit-nosetup.zip | FossHUB or Sourceforge.net |
codeblocks-20.03mingw-32bit-setup.exe | FossHUB or Sourceforge.net |
codeblocks-20.03mingw-32bit-nosetup.zip | FossHUB or Sourceforge.net |
NOTE: The codeblocks-20.03-setup.exe file includes Code::Blocks with all plugins. The codeblocks-20.03-setup-nonadmin.exe file is provided for convenience to users that do not have administrator rights on their machine(s).
NOTE: The codeblocks-20.03mingw-setup.exe file includes additionally the GCC/G++/GFortran compiler and GDB debugger from MinGW-W64 project (version 8.1.0, 32/64 bit, SEH).
NOTE: The codeblocks-20.03(mingw)-nosetup.zip files are provided for convenience to users that are allergic against installers. However, it will not allow to select plugins / features to install (it includes everything) and not create any menu shortcuts. For the “installation” you are on your own.
If unsure, please use codeblocks-20.03mingw-setup.exe!
Linux 32 and 64-bit
Distro | File | Download from |
---|---|---|
codeblocks_20.03_amd64_oldstable.tar.xz | FossHUB or Sourceforge.net | |
codeblocks_20.03_i386_oldstable.tar.xz | FossHUB or Sourceforge.net | |
codeblocks_20.03_amd64_stable.tar.xz | FossHUB or Sourceforge.net | |
codeblocks_20.03_i386_stable.tar.xz | FossHUB or Sourceforge.net | |
codeblocks-20.03-1.el6.rmps.tar | FossHUB or Sourceforge.net | |
codeblocks-20.03-1.el7.rmps.tar | FossHUB or Sourceforge.net | |
For Ubuntu, use this PPA |
Note: The Linux packages above are compressed archives (tar, tar.xz or tar.bz2). When you decompress the package you downloaded on your system, you will find all the .rpm or .deb packages required to install Code::Blocks.
Note: On RedHat/CentOS older revisions of 6 (up to 6.2 as far as we know) you need to add repoforge (former rpmforge) to your repolist, to be able to install the needed wxGTK-package. See http://repoforge.org/use for an instruction.
Note: Redhat/CentOS probably also needs an installed hunspell-package, if you want to install the contrib-plugins.
Mac OS X
File | Download from |
---|---|
CodeBlocks-13.12-mac.zip | FossHUB or Sourceforge.net |
NOTES:
- Code::Blocks 20.03 for Mac is currently not available due to issues caused by Apple hardening their install packages and lack of Mac developers. We could use an extra Mac developer to work on these issues.
- The provided download contains an Application Bundle (for the i386 architecture) built for Mac OS X 10.6 (and later), bundling most Code::Blocks plugins.
[Code::Blocks] Compile 64-bit under windows with MinGW-w64
Jan 9, 2017 · 2 min read
One of the great benefits of using Code::Block is that it is super easy to switch between compilers. In this blog, it shows how to add MinGW-w64 (GNU for Windows) to code blog and use it to compile a 64-bit program.
1. Install MINGW64
Download and install MinGW-w64. Assume that you install it under C:\mingw64.
2. Set up compiler
Open Code::Block. Go to Settings > Compiler. Under the drop down list of selected compiler, the GNU GCC Compiler should be selected by default. We will copy the settings of this compiler and then modify it.
Click on Copy and give a new name for the compiler that you are going to set up. You can name it whatever you want (e.g. GNU GCC Compiler (x64)).
One last step, you need to update the toolchain under the tab Toolchain executables. Modify the compiler’s installation directory to the directory of MinGW64 (e.g C:\mingw64). Also update the following under Program Files:
C compiler: x86_64-w64-mingw32-gcc.exe
C++ compiler: x86_64-w64-mingw32-g++.exe
Linker for dynamic libs: x86_64-w64-mingw32-g++.exe
Linker for static libs: x86_64-w64-mingw32-gcc-ar.exe
Now you can go ahead to use this compiler to compiler your program.
3. Set up debugger
With the above steps, you won’t be able to debug your program yet. You will probably get the following error message:
Now you have to set up the debugger under Settings > Debugger…. Select on GDB/CDB debgger, and Create Config. In the popup window, enter the name for the configuration. I am calling it gdb64 here. Under Executable path, select the corresponding gdb debugger for mingw64.
Finally, go back to the toolchain page for GNU GCC Compiler (x64), and switch the debugger to gdb64.