Pelles C forum
Pelles C => Announcements => Topic started by: Pelle on May 01, 2023, 05:15:49 PM
-
Pelles C version 12.00 (Release Candidate #2) is now available for download:
http://www.smorgasbordet.com/pellesc/download.htm
Changes for RC2:
- Removed declaration of __unreachable() from <intrin.h>
- Updated help file (typos, bad links, some text)
- Fixed C runtime problem with "%2lc" counting bytes, rather than characters, for a multibyte UTF-8 character.
- Fixed compiler problem with nested bit-field expressions.
- Fixed IDE problem with visible size not being updated when changing bitmap size through one of the drag handles.
- Fixed problem with missing BOM when saving modified text resource (HTML/MANIFEST/RCDATA).
Hopefully the last release candidate, with a release soon following...
/Pelle
-
RC2 install on Windows 11 64 bit, Controlled folder access blocked. See attached .pngs.
RC1 installs O.K.
-
I had similar problem. In my case the error was the impossibility to create files in the program folder. Rebooting the PC let me install the compiler...
I forgot: OS Win10.
-
I always install the Pelles C Compiler system to C:\Pellesc
I also exclude that folder from the Windows Defender scan list.
Release Candidate 2 installs and runs as expected for me.
-
It works fine here on Windows 10 with Firefox and installing to the default location, but I have dialed down the über-aggressive M$ security settings for years. The default policy seems to be (more or less) that if nothing can be installed, nothing bad can happen. This may make the computer secure, but also pretty useless.
There is no budget for a certificate for setup.exe, and placing everything in a ZIP file probably won't help much.
-
It works fine here on Windows 10 with Firefox and installing to the default location, but I have dialed down the über-aggressive M$ security settings for years. The default policy seems to be (more or less) that if nothing can be installed, nothing bad can happen. This may make the computer secure, but also pretty useless.
Who cares of them, now even my ultra-boring Norton-Antivirus says that the RC2 setup is safe :o :o :o
It usually annoys me with messages like "unknown origin", "too few users", Reputation threat, and the like... >:(
-
Installed fine on a WIN 11 fully up to date 22H2 64 bit system with GData antivirus, FireFox etc. Did install "for all users" .
Ran fine. Detected two items that previously given a pass in V11. First a quoted system include, for example "fileapi.h" which should have been <fileapi.h> passed in V11 needed fixing in V12.
Second a warning #2145 in V11 is now an error #2168 error in V12, on a 3rd party open source xlsx writer package from sourceforge.
V11 - Building XLXS_Output.obj.
C:\Program Files\PellesC\Files\vCardz\vCardz\XLXS_Output.c(187): warning #2145:
Using incompatible types 'FARPROC (aka int __stdcall (*)())' and 'WRITE_OPEN (aka (incomplete) struct xlsxio_write_struct * __stdcall (*)(const char *, const char *))'.
This one I'll need to figure out, as a warning it ran fine afaik.
John Z
-
Detected two items that previously given a pass in V11. First a quoted system include, for example "fileapi.h" which should have been <fileapi.h> passed in V11 needed fixing in V12.
So... what failed that needed fixing? A certain error code, or something else...?
Second a warning #2145 in V11 is now an error #2168 error in V12, on an open source xlsx writer package from sourceforge.
V11 - Building XLXS_Output.obj.
C:\Program Files\PellesC\Files\vCardz\vCardz\XLXS_Output.c(187): warning #2145:
Using incompatible types 'FARPROC (aka int __stdcall (*)())' and 'WRITE_OPEN (aka (incomplete) struct xlsxio_write_struct * __stdcall (*)(const char *, const char *))'.
Looks like return type 'int' vs '(incomplete) struct xlsxio_write_struct *', i.e. 'int' vs 'pointer'. For a Win64 project in Microsoft mode this would fail on '32 bits' vs '64 bits'. The quick and very dirty fix is to add a (FARPROC) cast somewhere needed, but I would recommend something better if possible ( FARPROC is not a great type in general, but may be hard to remove if it's part of a library by someone else ).
-
Detected two items that previously given a pass in V11. First a quoted system include, for example "fileapi.h" which should have been <fileapi.h> passed in V11 needed fixing in V12.
So... what failed that needed fixing? A certain error code, or something else...?
The fix was my error, sorry if not clear -
The quoted system H file was accepted as a 'valid?' H file in V11. In V12 the quoted system H file aborts the build with a message that it does not know how to build the fileapi.h include file. I had inadvertently used #include "fileapi.h" when I should have used #include <fileapi.h>....
Second a warning #2145 in V11 is now an error #2168 error in V12, on an open source xlsx writer package from sourceforge.
V11 - Building XLXS_Output.obj.
C:\Program Files\PellesC\Files\vCardz\vCardz\XLXS_Output.c(187): warning #2145:
Using incompatible types 'FARPROC (aka int __stdcall (*)())' and 'WRITE_OPEN (aka (incomplete) struct xlsxio_write_struct * __stdcall (*)(const char *, const char *))'.
Looks like return type 'int' vs '(incomplete) struct xlsxio_write_struct *', i.e. 'int' vs 'pointer'. For a Win64 project in Microsoft mode this would fail on '32 bits' vs '64 bits'. The quick and very dirty fix is to add a (FARPROC) cast somewhere needed, but I would recommend something better if possible ( FARPROC is not a great type in general, but may be hard to remove if it's part of a library by someone else ).
Thanks for the tips! It is part of a 3rd party lib. I'll give it a try.
John Z
-
In V12 the quoted system H file aborts the build with a message that it does not know how to build the fileapi.h include file.
Sounds like a change in project dependencies ("build rules"). Some IDE actions will trigger an automatic update, but it's not practical to detect every case, so there is also a manual "Update all dependencies" command. Whatever - since it apparently works now...
-
Hello Pelle!
Thank you for you work! This is very good news!
-
Hello Pelle!
Thank you for you work! This is very good news!
Thanks!
-
RC2 install on Windows 11 64 bit, Controlled folder access blocked. See attached .pngs.
RC1 installs O.K.
Reinstalled Windows 11. RC2 now installs without problem in default folder.
-
Reinstalled Windows 11. RC2 now installs without problem in default folder.
Good news. Thanks.