31
Help / Re: Can't build code blocks: Zip file structure invalid
« Last post by MadDavid on July 23, 2026, 07:14:59 pm »@stahta01. Thanks. That seems to work. Now I'm getting a failure farther into the process.
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
32
Embedded development / Re: MSP430 Programming with Debugging
« Last post by Miguel Gimenez on July 23, 2026, 11:16:17 am »Spam reported to moderator.
33
Embedded development / Re: MSP430 Programming with Debugging
« Last post by emelialucass on July 23, 2026, 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
-------------------------------------------
retro bowl
34
Help / Re: Can't build code blocks: Zip file structure invalid
« Last post by stahta01 on July 23, 2026, 01:54:35 am »Possible site https://fossies.org/windows/misc/zip300xn-x64.zip/
35
Help / Re: Can't build code blocks: Zip file structure invalid
« Last post by MadDavid on July 23, 2026, 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?
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?
36
Development / Bug: Code::Blocks does not save empty options fields.
« Last post by MadDavid on July 22, 2026, 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:
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
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.
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:
Quote
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
Quote
<LINK>in the compiler initialization. If you manually dele the cusom value, creating
<str>
<![CDATA[customvalue]]>
</str>
</LINK>
Quote
<LINK>then Code::Blocks will happily load it as an empty field.
<str>
<![CDATA[]]>
</str>
</LINK>
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.
37
Help / Re: Can't build code blocks: Zip file structure invalid
« Last post by Miguel Gimenez on July 22, 2026, 10:35:33 pm »Use a precompiled zip.exe, some toolkits include one.
38
Help / Can't build code blocks: Zip file structure invalid
« Last post by MadDavid on July 22, 2026, 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:
What do I do from here?
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:
Quote
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?
39
Nightly builds / Re: The 20 July 2026 build (13916) is out.
« Last post by christo on July 22, 2026, 07:25:28 pm »40
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?