1
General (but related to Code::Blocks) / Re: "which language"
« Last post by Miguel Gimenez on Yesterday at 09:15:43 pm »Are you using the wizard? Try selecting a Fortran project instead of a generic one.
News:
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
Recent Posts
2
Using Code::Blocks / Re: Frequent forum connection rejections.
« Last post by blauzahn on Yesterday at 07:40:25 pm »Here in Germany the site was slow to respond during the week. A few times even unavailable. Today, it seems to be okayish.
3
Using Code::Blocks / Frequent forum connection rejections.
« Last post by Pecan on Yesterday at 06:23:23 pm »Here in northern California, I'm getting frequent "cannot connect", "invalid gateway", timeouts trying to connect to the forum (https://forums.codeblocks.org).
Is anyone else having this problem?
I don't think that it's my internet provider because the codeblock forum site is the only one having this problem.
Is anyone else having this problem?
I don't think that it's my internet provider because the codeblock forum site is the only one having this problem.
4
Nightly builds / Re: The 24 March 2026 build (13828) is out.
« Last post by ccdric on Yesterday at 04:12:45 pm »here is the codeblocks patch to make generated binaries find plugins ( see attached)
Because the generated binary was unable to find the plugins. It looks like wxStandardPathsBase::Get().GetPluginsDir() doesn't work correctly and a previous patch for this didn't works with deb-helper
I'm not sure this codeBlocks patch will work in any linux distribution.
with this 2 patch everything is Ok to build on debian testing
you think it's possible to add this in a future nightly ?
Because the generated binary was unable to find the plugins. It looks like wxStandardPathsBase::Get().GetPluginsDir() doesn't work correctly and a previous patch for this didn't works with deb-helper
I'm not sure this codeBlocks patch will work in any linux distribution.
with this 2 patch everything is Ok to build on debian testing
you think it's possible to add this in a future nightly ?
5
Nightly builds / Re: The 24 March 2026 build (13828) is out.
« Last post by ccdric on Yesterday at 04:09:32 pm »anyway here are the attached files
6
Nightly builds / Re: The 24 March 2026 build (13828) is out.
« Last post by ccdric on Yesterday at 04:08:26 pm »attached is the post I tried to send (many time even without attached files) and it failed
Any Idee why ?
Any Idee why ?
7
Nightly builds / Re: The 24 March 2026 build (13828) is out.
« Last post by ccdric on Yesterday at 03:58:59 pm »sory for the previous test :-) I tried to post with code section and short attaced file ans i had this :
something goes wrong on this forum ?
Quote
Please try again. If you come back to this error screen, report the error to an administrator.
something goes wrong on this forum ?
8
Nightly builds / Re: The 24 March 2026 build (13828) is out.
« Last post by ccdric on Yesterday at 03:55:49 pm »test
9
General (but related to Code::Blocks) / "which language"
« Last post by Whissind on Yesterday at 09:45:22 am »When I try and set up for a new project, the IDE asks "which language" and Fortran isn't listed, only C and C++, whereas in a later frame "Fortran" is shown as the compiler. Can you explain why this is so? Is there something wrong?
10
Development / Re: It's year 2026, so I think some text like: 2024-2025 can be updated to 2026
« Last post by christo on April 02, 2026, 02:50:21 pm »I agree that migration to git is a great idea. It could be a game changer. svn is not used widely. Git is superior for collaboration by design as well as tools like github or gitlab.
I think moving to github/gitlab could bring in more developers as well, hence more features/ bug fixes. Also it allows us to upstream local changes easily by creating a pull request instead of creating a patch against an svn trunk version and uploading it to sourceforge via ticket. Now developers are not much familiar with the svn workflow.
Hi c::b developers, could you please consider moving codeblocks to github/gitlab?
Also it is a nice idea to move to a later version of c++.
Please let me know if I can do any help with these as I would like to help as code::blocks has helped me a lot.
I think moving to github/gitlab could bring in more developers as well, hence more features/ bug fixes. Also it allows us to upstream local changes easily by creating a pull request instead of creating a patch against an svn trunk version and uploading it to sourceforge via ticket. Now developers are not much familiar with the svn workflow.
Hi c::b developers, could you please consider moving codeblocks to github/gitlab?
Also it is a nice idea to move to a later version of c++.
Please let me know if I can do any help with these as I would like to help as code::blocks has helped me a lot.