Recent posts

#11

Bug reports / Re: Creating resource with man...

Last post by John Z - March 19, 2026, 10:06:02 AM

Hi PaoloC13,

I can't replicate the same problem because I uninstalled and reinstalled. It now compiles, but the .exe is broken. I suspect a file encoding issue (or some flag I haven't set?). You cannot view this attachment.

Attached a new version which compiles and runs with a simplified manifest.  If you add to it, do it step by step testing each addition

John Z

#12

Assembly discussions / Re: Verifying the support of t...

Last post by Vortex - March 19, 2026, 10:03:41 AM

Shorter 32-bit version and new upload above.

#13

Beginner questions / Re: same code pelles c and gcc...

Last post by ander_cc - March 19, 2026, 09:20:27 AM

Thank you, rweidner and John Z!

#14

Bug reports / Re: stdckdint.h bug report

Last post by ander_cc - March 19, 2026, 09:19:51 AM

I think ckd_<op>() came more or less straight from GCC to the C23 standard, and like some other GCC "innovations" it's a bit over-worked / under-thinked.

I will revise my initial implementation slightly, mostly just to reject more bogus cases -- like the original bug report.

Thank you, Pelle!

[_write()]

#15

Bug reports / Re: bug report. setvbuf() func...

Last post by ander_cc - March 19, 2026, 09:19:30 AM

In the low-I/O C runtime function _write(), when operating in text mode (ANSI/UTF-16LE/UTF-8/...), there is a ~2kB buffer for LF to CRLF translation. When this buffer is full, the content is sent to the destination (console/file/...), the buffer cleared, and the translation resumed. When resuming the translation the first character was lost (in translation).

( The printf family is one path to the _write() function )

Thank you, Pelle!

#16

Bug reports / Re: Creating resource with man...

Last post by TimoVJL - March 18, 2026, 11:39:45 PM

Just remove comments from xml file
like

Code Select Expand

    <!-- processorArchitecture="amd64" -->and use this line if it is common to X86 and X64

Code Select Expand

    processorArchitecture="*"

#17

Bug reports / Re: Creating resource with man...

Last post by PaoloC13 - March 18, 2026, 10:48:12 PM

I can't replicate the same problem because I uninstalled and reinstalled. It now compiles, but the .exe is broken. I suspect a file encoding issue (or some flag I haven't set?). You cannot view this attachment.

#18

General discussion / Re: Compiling using pomake

Last post by John Z - March 18, 2026, 08:57:56 PM

Yes, the povarsxx.bat files are generated at install time and are based on the directory (default, or user entered) during the install dialog.

To successfully run multiple versions is a bit more complicated however, thus the use of an xml file(s) as Timo mentioned.

John Z

#19

Announcements / Re: Release Candidate #1 for v...

Last post by Vortex - March 18, 2026, 07:05:24 PM

Hi Timo,

Thanks for the new tool. My result :

Code Select Expand

MOVBE not supported

#20

General discussion / Re: Compiling using pomake

Last post by rweidner - March 18, 2026, 06:31:26 PM

How project works with version 14 rc1 ?

It is possible to have many Pelles C versions in test PC

I interpreted this question in 2 different ways. Here are my interpretations and answers:

Interpretation 1:
Does project.bat work with PellesC 14?
Yes. I installed 14 RC 1 in the default location, and my program compiled and ran just fine using the project.bat script.

Interpretation 2:
What if a PellesC user has more than one version of PellesC on their PC? How would project.bat work in that case?

Somewhere near line 36 of project.bat there is a line like

Code Select Expand

call "%PROJECT_DIR%\env_pelles32.bat"
env_pelles32.bat:

Code Select Expand

@echo off
REM Sets PellesC environment for x86 builds.
call "C:\Program Files\PellesC\Bin\povars32.bat"

In case someone in the future reads this and doesn't already know, PellesC ships with 2 .bat files called:

- povars32.bat
- povars64.bat

This is what's in povars32.bat:

Code Select Expand

@echo off
set PellesCDir=C:\Program Files\PellesC
rem
echo Setting 32-bit environment for Pelles C...
rem
set PATH=%PellesCDir%\Bin;%PATH%
set INCLUDE=%PellesCDir%\Include;%PellesCDir%\Include\Win;%INCLUDE%
set LIB=%PellesCDir%\Lib;%PellesCDir%\Lib\Win;%LIB%

The answer to my interpretation of your question is, if someone had multiple PellesC installed and wanted to switch between them, at the moment they would need to modify env_pelles32.bat to point to the right version of PellesC. What I don't know is whether or not those 2 .bat files are dynamically generated at install time. (povars32.bat, povars64.bat) If not, they might also need some tweaks.