Recent Posts

Pages: 1 ... 4 5 6 7 8 [9] 10
81
General (but related to Code::Blocks) / Re: OpenWatcom (W32) Compiler template problem
« Last post by Tim on November 29, 2025, 12:48:24 pm »
Another update...


It looks like I've only got it partially right, depending on which CB version I'm using.

On CB 8.02 it 'appears' no copies of the Watcom compiler template of will work in multi obj file senarios.
This is because the 'file' directive and the obj file ',' comma separator are hard-coded, and don't come across in the template copy.

The 'file' directive is not a problem as it can be added to the command line macro.
But the obj file list comes pre-built via the '$link_objects' variable, and I can't see a way to change it.
However later versions of CB have user selectable separator character.

So for CB 8.02, the upshot would 'appear' to be, that all different Watcom compiler builds need to be modifications of the original "OpenWatcom (W32) Compiler" template which cannot be saved as a copy.

That said, perhaps I'll discover another twist tomorrow.

Maybe as CB 8.02 and Watcom Dos 16bit builds are more likely to be used with Windows 98se it strikes me as worth thinking about rebuilding it with a revised "OpenWatcom (W32) Compiler" template and a user selectable separator character option.
82
Using Code::Blocks / Re: Code::Blocks and Intel OneAPI?
« Last post by ThierryD on November 29, 2025, 12:15:01 pm »
Hi,

I answer ... to me...  :D
Spam ?

Then, after some try and research, you can use both Intel OneAPI compiler 2025.3 (latest releade) leaned with Visual Studio 2026 (latest release) into CB,with some ligth changes on your environment configuration ("symbolic" link added, and two env var positioned with "correct" value) on Windows 11 25H2 64 bit. Joined text to understand how.

Regards.
83
General (but related to Code::Blocks) / Re: OpenWatcom (W32) Compiler template problem
« Last post by Tim on November 28, 2025, 01:55:00 pm »
I've now found a "Work Around" for the problem, which I think will also help to define the problem.

My original aim was to create a compiler template to produce Watcom dos16 applications using both wcl.exe and wlink.exe.

Working on a fresh copy of XP (SP3) and a fresh CB 8.02 install, I would:-


1. Create a copy of "OpenWatcom (W32) Compiler" template and name it "Copy1".

2. Modify the "Copy1" template with the necessary changes to build a Dos16 App.

3. Create a new Dos console project "wd1" specifying the "Copy1" template for the compiler.

The Problem............
The full command would be reported as I expected it to look, but the
build would fail but without reporting any actual results or warnings or errors.


The "Work Around".........


1. Modify the original "OpenWatcom (W32) Compiler" template with the necessary changes to build a Dos16 App.

2. Create a copy of the "modified" "OpenWatcom (W32) Compiler" template and name it "Copy2".

3. Create a new Dos console project "wd1" specifying the "Copy2" or  the modified "OpenWatcom (W32) Compiler" template for the compiler.

The build will now work correctly, and report results and any actual warnings or errors correctly if any are introduced to the source files.


I have not tested the "work around" on CB 20.05, only on  CB 8.05

After I install CB 20.05  I have to apply a patch
https://forums.codeblocks.org/index.php/topic,23924.msg167864.html#msg167864
to the installation before it will run

It would seem that CB 25.03 may also need a similar patch to run on XP
A message box appeared similar to:-    api-ms-win-crt-convert-l1-1-0.dll was not found.

***********************

In 2000 I was acutely embarrassed when trying demonstrate some bespoke software
to a room full of executives, only to be met with a message msvc runtime dll not found.
After that I bought a PC for testing only, and invested in a copy of Installshield.

Soon after that I experimented in copying OS's to harddisks with multiple primaries, to speed
up the process of obtaining fresh OS test installations. I briefly described my method here :-
https://www.xpforums.com/threads/open-file-security-warning-do-you-want-to-open-this-file.935598/#post-3274916

Although it's still a pain to test with each OS, at least it can usually still be done on the same development PC,
and only takes about 5 minutes per OS to get the answer to "will it run?".
84
Development / Setup With MinGW-w64 Bundled
« Last post by popcatuwu on November 28, 2025, 12:41:46 am »
I know you can use Code::Blocks with an external MinGW-w64 compiler, but that requires setup. Currently, the only compiler bundled in the setup is MinGW, which is a 32-bit compiler. Will we ever get C::B with MinGW-w64 bundled in a certain version of setup?
85
Help / Re: How to fix the translation error of zh_CN
« Last post by gd_on on November 27, 2025, 02:11:11 pm »
Effectively, in zh_CN.mo as distributed on C::b web site (at least in the nosetup.zip version), there is this error (but I can't correct that). Probably, this zh_CN had a problem or was not updated as it should. The last version on launchpad, .po and .mo are OK and more, has been regularly updated (last contribution by Grit Clef: 2025-10-01)
86
Help / Re: How to fix the translation error of zh_CN
« Last post by Cubestone.Wang on November 27, 2025, 12:48:06 pm »
First, thank you for answer. I just finished to change it for myself.

And then, I see the new website and download it, the content translation is right ( translated on 2019-06-21, reviewed on 2024-03-27)



So, the question: I download software package (version 25.03) from "https://www.codeblocks.org/downloads/binaries/#imagesoswindows48pnglogo-microsoft-windows". And the zh_CN file just is built-in (2025-03-31). When you use "msgunfmt zh_CN.mo -o zh_CN.po" to check it, just see "!" in content (just like what I said). Anyone who interested in it could do these step for check.




Thus, what's happened? May in CI/CD process, it is not get ".po" file from the new translate website?
87
Help / Re: How to fix the translation error of zh_CN
« Last post by gd_on on November 27, 2025, 11:58:28 am »
More, from this page you can also download the .po file (source) and/or the .mo file. If you have still problems, you can try to use poedit on the .po file to correct it and produce your own .mo file. You can also correct some bad or not correct translations on launchpad and submit them (you just need to have already a launchpad account or create one).
88
Help / Re: How to fix the translation error of zh_CN
« Last post by Miguel Gimenez on November 27, 2025, 11:44:37 am »
The launchpad page you saw is obsolete, please use this
89
Help / How to fix the translation error of zh_CN
« Last post by Cubestone.Wang on November 27, 2025, 10:05:20 am »
When I use 25.03 version in zh_CN, there is a "!" before the content, see the following image:

After using "msgunfmt zh_CN.mo -o zh_CN.po", I confirm it:

And then, I search something, but in source code, no zh_CN file, in Nightly builds, no zh_CN file, in translate website, the current content is translated just in 2006-07-17:




So where is the question, in building process?
I post the message in this forums, and wait someone could fix it. Or maybe post it in "https://sourceforge.net/p/codeblocks/tickets/"?
90
General (but related to Code::Blocks) / OpenWatcom (W32) Compiler template problem
« Last post by Tim on November 25, 2025, 05:41:59 pm »
System = Windows XP SP3

Codeblocks 8.02 and 20.03 (Possibly others in between)

I've just noticed a problem with the "Open Watcom" compiler template/Plugin.

If a "copy" is made of the "OpenWatcom (W32) Compiler" template, Say for example,  "Copy of OpenWatcom (W32) Compiler" (Without any modifications)

Then an attempt to compiler & link a basic "Console" application with it, it will generate a very different warning & error output from the original template.
Pages: 1 ... 4 5 6 7 8 [9] 10