Recent Posts

1

Embedded development / Re: MSP430 Programming with Debugging

« Last post by emelialucass on Today at 06:40:30 am »

The mspdebug version included in the Texas Instruments toolchain requires libcurses.so.5 and libtinfo.so.5, which are incompatible with Debian 13's transition to version 6 of these libraries.
-------------------------------------------
retro bowl

2

Help / Re: Can't build code blocks: Zip file structure invalid

« Last post by stahta01 on Today at 01:54:35 am »

Possible site https://fossies.org/windows/misc/zip300xn-x64.zip/

3

Help / Re: Can't build code blocks: Zip file structure invalid

« Last post by MadDavid on Today at 12:06:50 am »

NONE of my toolkits (Code::Blocks 20, LLVM, Python310, TDM-GCC-64 MinGW, Visual Studio) contain a command-line zip tool.

When I click the link at the bottom of this page: https://wiki.codeblocks.org/index.php/MinGW_installation#Development_Tools, I get a message from Firefox that I need to select an application to open that link.

When I look online for how to open an FTP link, everything says that FTP is no longer supported in browsers, and you should use FileZilla or some such.

When I put the FTP site into FileZilla, the request to open the FTP size times out.

I'm not even sure that this is really a problem with my compiled Zip tool, because it created a zip file that Windows can open.

So, where do I get a valid precompiled zip.exe?

4

Development / Bug: Code::Blocks does not save empty options fields.

« Last post by MadDavid on Yesterday at 11:02:32 pm »

I'm trying to get Code::Blocks working with LLVM CLANG.

CLANG uses clang-cl to pass linker commands onto Visual Studio's Link.exe in order to link Windows GUI project into a windows executable.
clang-cl and link.exe require .lib files to *not* have a "link library (e.g. -l)" parsing option in the command line.  When I try to compile, I get this in my build log:

clang-cl: warning: unknown argument ignored in clang-cl: '-lgdi32.lib' [-Wunknown-argument]
clang-cl: warning: unknown argument ignored in clang-cl: '-luser32.lib' [-Wunknown-argument]
clang-cl: warning: unknown argument ignored in clang-cl: '-lkernel32.lib' [-Wunknown-argument]
clang-cl: warning: unknown argument ignored in clang-cl: '-lcomctl32.lib' [-Wunknown-argument]
clang-cl: warning: unknown argument ignored in clang-cl: '-lgdi32.lib' [-Wunknown-argument]
clang-cl: warning: unknown argument ignored in clang-cl: '-luser32.lib' [-Wunknown-argument]
clang-cl: warning: unknown argument ignored in clang-cl: '-lkernel32.lib' [-Wunknown-argument]
clang-cl: warning: unknown argument ignored in clang-cl: '-lmsvcrt.lib' [-Wunknown-argument]

as well as "LNK2019: unresolved external symbol" errors for every function I'm calling from those libraries.

When I
*  go to Settings > Compiler... > [My Windows Compiler] > Other settings > Advanced options...,
*  Go to Others in "Advanced compiler options"
*  Select the contents of "Link library (e.g. -l):
*  Delete to clear the contents,
*  Click "OK", "OK"
and build the project, the project builds successfully.


Here's the bug:
When I save everything, close Code::Blocks, and reopen Code::Blocks, [My Windows Compiler] has reverted the  "Link library" field to "-l", forcing me to manually clear it again.
This is because when Code::Blocks saves default.conf, it skips over empty text fields instead of saving the empty value.
If you create a custom value in that field, then default.conf contains

               <LINK>
                  <str>
                     <![CDATA[customvalue]]>
                  </str>
               </LINK>

in the compiler initialization.  If you manually dele the cusom value, creating

               <LINK>
                  <str>
                     <![CDATA[]]>
                  </str>
               </LINK>

then Code::Blocks will happily load it as an empty field.

But every time you close Code::Blocks, the empty fields get left out of default.conf, reverting them to default values.

SOLUTION:
Please write empty fields as <![CDATA[]]> instead of skipping them.  "No value." may be important information to preserve.

5

Help / Re: Can't build code blocks: Zip file structure invalid

« Last post by Miguel Gimenez on Yesterday at 10:35:33 pm »

Use a precompiled zip.exe, some toolkits include one.

6

Help / Can't build code blocks: Zip file structure invalid

« Last post by MadDavid on Yesterday at 10:30:48 pm »

I'm trying to build code::blocks from source to figure out how to fix a bug that prevents LLVM from linking windows executables together.

I built the zip.exe utility from source as well, put a path to it, and tried building the CodeBlocks_wx32_64.cbp

Everything seemed to run well until it got to the post-build steps, at which point it coughs up this error:

Running target post-build steps
cmd /c if not exist devel32_64\share\CodeBlocks mkdir devel32_64\share\CodeBlocks
zip -jq9 devel32_64\share\CodeBlocks\manager_resources.zip sdk\resources\*.xrc
cmd /c "cd sdk\resources & zip -0 -q ..\..\devel32_64\share\CodeBlocks\manager_resources.zip images\*.png images\8x8\*.png images\10x10\*.png images\12x12\*.png images\16x16\*.png images\20x20\*.png images\24x24\*.png images\28x28\*.png images\32x32\*.png images\40x40\*.png images\48x48\*.png images\56x56\*.png images\64x64\*.png images\svg\*.svg"
zip error: Zip file structure invalid (../../devel32_64/share/CodeBlocks/manager_resources.zip)
Process terminated with status 3 (0 minute(s), 53 second(s))
1 error(s), 30 warning(s) (0 minute(s), 53 second(s))

What do I do from here?

7

Nightly builds / Re: The 20 July 2026 build (13916) is out.

« Last post by christo on Yesterday at 07:25:28 pm »

Hi,

AppImage for x86_64 Linux is available for download here

This requires GTK-3.0 installed.

Please give execution permission and double click or launch from terminal.

Detailed steps to run AppImage is available here

8

Help / Re: Trouble opening Code::Blocks on MacOS

« Last post by Miguel Gimenez on July 21, 2026, 07:31:51 pm »

That message should be harmless, it only means spell checking will not be available. Does C::B start afterwards?

9

Help / Trouble opening Code::Blocks on MacOS

« Last post by Martin on July 21, 2026, 04:06:52 pm »

Good day,
I downloaded Code::Blocks for MacOS (current version: Tahoe 26.5.2 ), but when I try to open it, it displays a debug report and a separate warning message,

"One or more plugins were not loaded.
This usually happens when a plugin is built for a different version of the Code::Blocks SDK.
Check the application log for more info.
List of failed plugins:
libSpellChecker.dylib"

I am pretty unfamiliar with MacOS as well as the Code::Blocks environment and I am far from tech savvy. I also tried attaching a screenshot, but I'm not sure how the "Insert Image" button works. My university has made the use of Code::Blocks compulsory for my current module, therefore it is urgent for me to resolve this issue.

Please get back to me as soon as you can. My apologies for any frustrations caused.

10

General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!

« Last post by Martin on July 21, 2026, 03:36:28 pm »

I am new, I am here