Activity for Code::Blocks
-
ollydbg posted a comment on ticket #1534
Hi, Morten, I report an issue about this change here: The library search path is not included in the PATH in the compilergcc plugin
-
Miguel Gimenez committed [r13739] on SVN Repo
* Fix assertion loading a big project with a hidden project manager.
-
Tomasz Pawlak posted a comment on ticket #1555
Version 2 of this patch: - Fixed: Removed unused variables: ppStream::Emtx PipedProcess::m_evtline, - Fixed: ppListenerThread::Entry(): no need to set thread name after restart - CompilerGCC does not change the process index, - Fixed: PipedProcess::Launch(): no need to close strmxxx->m_fds on error, - Fixed few comments
-
- Refactor CodeBlocksApp::ParseCmdLine(), no functional changes.
-
* Use monospaced font in the command line help dialog (seen when executing codeblocks -h).
-
ScintillaWX - remove hash map for timers
-
PipedProcess for Linux patch
-
pecan committed [r13736] on SVN Repo
- BrowseTracker - commit missing images
-
* BrowseTracker: 1.4.131 25/09/17 Apply Christo "Jump to last modified" patch (Thanks Christo)
-
clangd_client : fix crash on completion response after project closed
-
clangd_client : fix crash on completion response after project closed
-
Applied, rev 13734, thanks Christo
-
* Clangd_client: 1.2.142 2025/09/20 Apply Christo 1554 patch and guard like use of pParser. (Thanks Christo)
-
Christo created ticket #1554
clangd_client : fix crash on completion response after project closed
-
Code::Blocks released /Binaries/Nightlies/2025/CB_20250913_rev13733_win64.7z
-
- BrowseTracker: Remove warning about comparing signed and unsigned integers.
-
Federico Perini posted a comment on ticket #1546
Thanks a lot @mortenmacfly (and previously @wh11204). Yes I realize the patch was too big - sorry, it took quite a few changes to bootstrap C::B on macos.
-
Morten MacFly committed [r13732] on SVN Repo
* fix for previous commit: accidentally committed wrong file
-
Running compiled program fails because of wrong PATH
-
Running compiled program fails because of wrong PATH
-
I've added a convenience function for that purpose in [r13731]. With the next nightly, this issue should be solved.
-
* provide convenience function to fix bug #1534: Running compiled program fails because of wrong PATH
-
* compilation fix for non-PCH compilers
-
- eliminated white-spaces / wrong indention introduced with recent commits
-
Patch: enable GCC to parse Fortran warnings
-
Applied in SVN [r13728] Thank you!
-
* applied patch #1545 Patch: enable GCC to parse Fortran warnings by Federico Perini
-
Fix crashes when building/running C::B on macOS-arm + clang++
-
For 1) this is applied in [r13724], [r13725], [r13726] ad [r13727] Thank you! For 2) this was already fixed in an earlier commit. Next time, please consider providing a single patch for each different item individually, this helps us applying patches easily.
-
* partially apply patch #1546 Fix crashes when building/running C::B on macOS-arm + clang++ (code completion robustness), by Federico Perini
-
* partially apply patch #1546 Fix crashes when building/running C::B on macOS-arm + clang++ (jumptracker robustness), by Federico Perini
-
* partially apply patch #1546 Fix crashes when building/running C::B on macOS-arm + clang++ (multiline dialog robustness), by Federico Perini
-
* partially apply patch #1546 Fix crashes when building/running C::B on macOS-arm + clang++ (layout saving), by Federico Perini
-
Bootstrap: C::B requires automake 1.13 or newer.
-
Applied in SVN [r13723] Thank you!
-
* applied patch #1550: Bootstrap: C::B requires automake 1.13 or newer (by Carlo Bramini)
-
Are you aware that you can actually edit the wizard your self, adjust and provide a patch? would you be willing to do so?
-
- Remove wxWidgets 3.1 projects and workspaces.
-
* BrowseTracker: Add missing editor activations to jump tracker array
-
clangd_client : avoid crash when compiler in project file not available
-
Applied rev 13720 Thanks
-
clangd_client : fix crash on reparse
-
Applied rev 13720 Thanks
-
* ClangdClient: Apply patches 1551 and 1552 (Thanks Christo)
-
RoyalX posted a comment on ticket #1553
i'm using C::B svn 13710 on Win 11
-
C::B does not link libwxlexilla.a when creating a wxWidgets 3.3 project with wxSTC
-
clangd_client : fix crash on reparse
-
clangd_client : avoid crash when compiler in project file not available
-
- HexEditor: Apply part of the changes suggested by Cppcheck.
-
Carlo Bramini created ticket #1550
Bootstrap: C::B requires automake 1.13 or newer.
-
* adjust silent installer of release to validate against checks from MS App Store: Remove splash screen in silent install
-
* updated two references of bzlib2 to Gitlab version (applied to help- and SpellChecker-plugin) and adopted C::B comments
-
Patch: enable GCC to parse Fortran warnings
-
Patch: enable GCC to parse Fortran warnings
-
This patch does not apply safely on SVN trunk. Could you please try again? Just checkout the clean to SVN/trunk head revision, apply your changes and then run: svn diff > my.patch ...on the command line. Thank you!
-
change visual state of file only if it is not controlled by vcs
-
Patch: update zlib 1.2.8 -> 1.3.1
-
Patch: update zlib 1.2.8 -> 1.3.1
-
Applied in SVN, [r13716] . Thank you!
-
* applied patch #1548: update zlib 1.2.8 -> 1.3.1 by Federico Perini
-
change visual state of file only if it is not controlled by vcs
-
That annoyed me for a while, too. Thank you, applied in [r13715] .
-
* applied patch #1549 by Christo: change visual state of file only if it is not controlled by vcs
-
change visual state of file only if it is not controlled by vcs
-
Klaus Kusche posted a comment on ticket #1534
In the descriptions of the exercises, there is also a description on how to set up the project for each exercise. So the students are expected to be able to set up their projects by themselves in CB's build options: They should learn what compiler and linker options are, how header and lib dir's work and so on for projects with additional libs. Approximately one third of the students manages to set up their projects correctly by themselves, and the other two thirds mess it up and need my help......
-
Patch: update zlib 1.2.8 -> 1.3.1
-
I downloaded svn 13710. I can confirm that after fix [r13705], Scale Factor is now taken into account. The text size has become slightly larger, but it is still uncomfortably small. I would like the text size in the Disassembly, Memory Dump, and CPU Registers windows to be customizable, or at least to match the value in Settings > Debugger > Value Tooltip Font.
-
I downloaded svn 13710. I can confirm that after fix [r13705], Scale Factor is now taken into account. The text size has become slightly larger, but it is still uncomfortably small. I would like the text size in the Disassembly, Memory Dump, and CPU Registers windows to be customizable, or at least to match the value in Settings > Debugger > Value Tooltip Font.
-
I downloaded svn 13710. I can confirm that after fix [r13705], Scale Factor is now taken into account. The text size has become slightly larger, but it is still uncomfortably small. I would like the text size in the Disassembly, Memory Dump, and CPU Registers windows to be customizable, or at least to match the value in Settings > Debugger > Value Tooltip Font.
-
- CodeCompletion: Add missing optimization in r13711.
-
Sorry I uploaded an incomplete patch file - the correct one is attached. Also - do let me know if we should split the zlib update from the codecompletion pointer crash update. Thank you, Federico
-
Sorry I meant "parsing Fortran-related compiler warnings", not "parsing Fortran input files".
-
IncrementalSearch: macOS fix
-
Applied in [r13713], thank you. Patch modified to keep code style and remove non-ASCII characters in comment.
-
* IncrementalSearch: Fix search bar resetting on Mac (ticket #1547, thanks Federico Perini).
-
wxDirData assert failed in rev13667 on Ubuntu
-
Should be fixed in [r13712].
-
* CodeCompletion: Remove assertion in wxDir when the filename has no path (ticket #1544).
-
IncrementalSearch: macOS fix
-
Sorry I uploaded an incomplete patch file - the correct one is attached. Thank you, Federico
-
Fix crashes when building/running C::B on macOS-arm + clang++
-
Patch: enable GCC to parse Fortran warnings
-
Unfortunately, for some of our exercises we need the old gcc, and some depend on the new gcc. Ah, you explained it here. So you really have mixed exercises that require different compilers. Therefore these are in different projects, right? Who creates these projects? The students? You could provide a customised project template with a post-build project step that always copies the right DLLs to the right BIN folder. Using macros you can do this in a generic fashion that would work for all compil...
-
Unfortunately, for some of our exercises we need the old gcc, and some depend on the new gcc. Ah, you explained it here. So you really have mixed exercises that require different compilers. Therefore these are in different projects, right? Who creates these projects? The students? You could provide a customised project template with a post-build project step that always copies the right DLLs to the right BIN folder. Using macros you can do this in a generic fashion that would work for all compil...
-
Running compiled program fails because of wrong PATH
-
OK, so what I don't get: You have 2 compilers installed, you need only one. Right? Why don't you uninstall the one that is conflicting? There are also C::B installers w/o the compiler. You could also invalidate its config by changing the master path. Maybe I still misunderstood your requirements?
-
- add Christo to about dialog
-
-
Checked your alternatives. They are not valid alternatives in our environment. We are not talking about the CB I use (in fact, I do not use CB. I compile on the command line for 45 years now...). We are talking about the 200 CB's installed in the computer labs of our university for the beginner's programming courses. Most of these students have never used the command line, have never heard of PATH, and don't know what static linking is. They type their program, hit the "Build and Run" button and...
-
Question: Is the PATH constructed for the "Run" button project-independent, or is it constructed individually whenever "Run" is clicked depending on the project settings? It needs to be set depending on the project being run and the compiler set for this project!
-
- Clangd_client: Use 0 to initialize size_t, not nullptr.
-
You describe correctly and exactly what should happen (and what I want to happen, that's why I opened this ticket): "Prepending the selected compilers bin-folder to the PATH is required ...." (i.e. the compiler selected for the project should be first in the PATH, preceeding the default compiler). But exactly the opposite of what you said is actually happening in CB: The selected compiler's bin-folder is appended (not prepended) to the PATH, i.e. it is after the bin-folder of the default compile...
-
Joshua posted a comment on ticket #1526
That's strange, because I downloaded and installed version 25.03 from official website download link 4 days ago: https://sourceforge.net/projects/codeblocks/files/Binaries/25.03/Windows/codeblocks-25.03mingw-setup.exe Maybe the modified code was not merge into the release branch?
-
We had updated the installers to reflect this a long time ago. Is that really still the case? I would wonder...
-
clangd_client : if filterText not present in completion response, use label instead
-
Applied in SVN, [r13709]. Thank you!
-
* applied patch #1542 by Christo: clangd_client : if filterText not present in completion response, use label instead
-
clangd_client : some stability fixes
-
clangd_client : some stability fixes
-
Applied patch in SVN, [r13708]. Thank you!
1 >
