Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
Exact same thing happening to me. Tried with a fresh windows install, downloaded codeblocks-20.03mingw-setup.exe and can't even run the "Hello world" program. No weird file names, compiler directory is correct, everything that should be checked is checked
Using Code::Blocks / Re: Compiling only - is there a bug or it is me ?
« Last post by Miguel Gimenez on September 15, 2021, 10:14:52 pm »
Are you really using two backslashes after E:? This can confuse wxFileName, see for example this pull request for wxWidgets.
Using Code::Blocks / Re: Compiling only - is there a bug or it is me ?
« Last post by stahta01 on September 15, 2021, 09:29:46 pm »
It sounds like you did something very wrong or you are not using an Code::Blocks project.

If using an Code::Blocks project, all you need to do is:
Right click on file, select option, un-check "link file".

Tim S.
Using Code::Blocks / Compiling only - is there a bug or it is me ?
« Last post by Elena on September 15, 2021, 09:04:56 pm »
Hi, I am trying to set up a project for compiling only without linking (with GCC, winLibs). I am using the latest Nighlty Build of CB. After some trials and errors I *think* I found that I must specify Type = Commands Only in project properties, and in fact it issues g++ with the -c option which sould indeed mean compile only without linking. I would therefore expect all my .o files created in the usual objs dir inside my project dir.
Not instead. If my cb  project is say E://MyProjects/NewProject/NewProject.cbp the .o files are placed in E:// directly !!!
Is it a bug which I should report or I did something wrong ?
If you can reply soon I would be grateful. Thx.
Help / Re: CodeBlocks Crashing
« Last post by AndrewCot on September 15, 2021, 11:01:38 am »
I am 100% in agreement with Miguel's august nightly.

I am very familiar with C::B windows compiler detection. IMHO make sure the MinGW-w64 compiler is in C:\mingw64 instead of "C:\Program File (x86)...."

The zip for the compiler is:

If you get stuck you can always change the compiler as follows:
1) Open the compiler settings dialog via the settings->compiler menu option
2) In the drop down list select "GNU GCC Compiler"
3) In the tab control select "Toolchain executables"
4) Change the compiler installation directory to the directory where you have the mingw-w64 compiler installed.

Help / Re: CodeBlocks Crashing
« Last post by Miguel Gimenez on September 15, 2021, 09:36:04 am »
IMHO the august nightly is a lot more stable and feature rich than 17.12 or 20.03, and you can use the 17.12 tutorials without changes.

Bugs are posted here

EDIT: before posting a bug in 17.12 or 20.03 please check if it is fixed in the nightly.
Help / Re: CodeBlocks Crashing
« Last post by MrBadAttitude on September 15, 2021, 06:27:11 am »
I can't reproduce the issue; SortTemplates() did crash some time ago (see this thread, but it was related to a change after 20.03 was released.

Can you try a recent nightly?. Just download the three zip files and extract them in a folder of your choice. It can coexist with 20.03.

I was able to use it with the nightly version the only problem was that the GNU GCC Compiler was not detected(I am sure I can fix this problem). Rather than using an unstable version of a software I just gonna use the 17.12 version which is more than enough because the C and C++ programming tutorials that I am watching are using much more older versions of CB. But could you please let me know where I can report bugs so that I can report it and let it be fixed later on?

Thank you.
I have uploaded a new NSIS x64 installer with the changes to hopefully resolve the issues, with the exception of the Additional page icons. I have updated the Installer_Pages.odt to show the updated and new pages in this release.

My feedback on your feedback is:
1. We only use NSIS, there is no need for an ISS based installer, we won't ship both. The ISS script is a relict from very old times
    - NSIS was superior 10 years ago compared to ISS, but ISS has improved a hack of allot and is up to the job now. ISS apart from installing the components via a selectable list is allot easier to follow and program and enhance compared to NSIS based on my usage of both over the last few months.
    - ISS uses pascal instead of a what appears to be some custom programming language that is not easy to understand or use compared to normal programing languages.
    - There are ISS IDE's and GUI's to make it easier to create the script. But there is no specific NSIS IDE that make it easier to update/change the script.
    - Both are not very good for creating a new GUI from scratch, but ISS has a bunch of templates you can use that make it a bit easier.

    I agree to only ship one, but going forward the ISS script will be allot easier to maintain IMHO.

2. The logo is from CodeBlocks Version 1 which is around 20 years ago...?! :-) So it should be updated
    - Fixed: rotated the current logo and cropped it and moved some of the text around, added text.

3. Did you try to run the installer in an unattended mode w/o GUI? this must work.
    - C::B 20.03 - silent install pops up the splash screen
    - Fixed/Updated:
        a. Installs in C:\Users\andrew\AppData\Local\Programs\CodeBlocks if run as normal user with /S, but now does not pop up the spash dialog
        b. Fixed admin unattended install for C:\program files.\
        c. Updated the script to define MULTIUSER_INSTALLMODE_COMMANDLINE

4. It would be nice if one could skip the creation of shortcut (but its not a must)
    - Fixed:
        This is in the custom setup like in the 20.03 installer from what I can see. It is not easy to find.
        Updated script for newly added shortcuts from missing apps.
    - Fixed:
        In the new installer if you run the custom install you can also select on the "Choose Start Menu Folder" there is a tickbox for "[ ] Do not create shortcuts" under the start menu folder list.
        Updated script for mising macros.

5. Under additional icons: If I un-select all, what is actually created in that case? For me its nothing, so why are these on the "Additional" page?
    - Need more info.

6. The Un-installer did not work well for me. It left tons of files, including all plugins and the executable.
    - Problem:
        If you install as admin for all users and then run the installer as a user the files are shown as to be removed on reboot, but they are not.
    - Fix/work arround:
        If you install for all users then you need to run the uninstaller as admin otherwise it will pop up and tell you to run the uninstall again with admin rights.
        Added support for detecting if C::B was allready installed and by privelege in order to either ask the user to uninstall the previous version or run the installer as admin or as a normal user.
        Added support for uninstalling 20.03 before installing update on x64 system as they are in different directories and may use different registry uninstall kys (HKLM or HKCU depending on install rights used)
    - Hopefully I have covered the different options so files are not left, but if they are can you let me know how the previous version was installed (and if it was 20.03) and how the new installer was run (admin or normal user rights) and where the files that were left are (C:\program files, C:\program files (x86), C:\users......).

7. But, for people w/o internet connection (and these are many) there should also be a  package that has our default compiler bundled. This is also related to running in  unattended mode for admins and alike.
    - Updated the download compiler page to not be shown if is no internet connection.
    - Created a new page to install the following files if they exist (if they both don't exist the page is not shown)
            * i686-8.1.0-release-posix-dwarf-rt_v6-rev0.7z
            * x86_64-8.1.0-release-posix-seh-rt_v6-rev0.7z
          They files are available from:
          The new page could be modified in the future to add more files or use the files from a text file if the text file exists in the same directory, but someone else can do this.

     - I do not like bundling the compiler as this causes newbies to think that C::B is the compiler........wrong!!!

     -  The way MINGW is bundled in 20.03 is not documented w.r.t. what goes into the "\MinGW" directory that the 20.03 nsi script uses. This change makes it consistent in that the files are sourced from the mingw release and are not modified in any way.
    - The new page installs the compilers in C:\mingw32 or c:\mingw64 by default, which is allot better than the 20.03 default directory. These two directories are also the default mingw installer.

Let me know if there are any other changes or mods or updated or queries etc etc.
Updated release now available for x64.

The main changes are with the installer and manual incorporation of SF ticket 1135 patch.

The installer changes are:
    30. Install and uninstall checks to see you are running as admin or normal user so the install/uninstall uses the same priveleges as last one.
    31. Modified nsi to only show the download compiler page if an internet connection is detected.
    32. Modified nsi to support installing the following if they are in the same directory as the installer:
            * i686-8.1.0-release-posix-dwarf-rt_v6-rev0.7z
            * x86_64-8.1.0-release-posix-seh-rt_v6-rev0.7z
          These can be downloaded from

The NSIS changes are incorporated into the Installer_Pages.odt file, which you can open in MS Work or LibreOffice.
Using Code::Blocks / Re: How do I add new downlaoded header files to codeblocks?
« Last post by stahta01 on September 15, 2021, 03:34:16 am »
Add the folder to the project search path.
Post the Code::Blocks build log to help us help you.

How to add folder to the project search path:

Project -> Build Options
Tab: Search directories
Sub-Tab: Compiler
Button: Add
Button that looks like an folder
Enter path that contains folder
If asked to keep this path as relative? Click yes
Click OK if needed

Tim S.

Pages: [1] 2 3 4 5 6 ... 10