- Welcome to Pelles C forum.
Pelles C forum
News:
Download Pelles C here: http://www.pellesc.se
Recent posts
#71
Graphics programming / Re: raylib 5.5 + PellesC v13.0...
Last post by rweidner - March 04, 2026, 09:23:43 PMWow, Vortex. That is an interesting problem. I'll look at this more closely. I might have run into this too, sooner or later. What's interesting is that if you look at the raylib.h file on lines 1323, 1475, 1476, and 1649, raylib didn't define LoadImageA, DrawTextA, DrawTextExA, or PlaySoundA. This smells like some macro voodoo to me.
Question: For whatever reason it was that you included windows.h is it necessary that windows.h is included in the same file as raylib.h? Would a separate .c file help so that raylib.h and windows.h are not included in the same file?
Question: For whatever reason it was that you included windows.h is it necessary that windows.h is included in the same file as raylib.h? Would a separate .c file help so that raylib.h and windows.h are not included in the same file?
#72
Graphics programming / Re: raylib 5.5 + PellesC v13.0...
Last post by Vortex - March 04, 2026, 08:13:59 PMHello rweidner,
Thanks for the sample, I managed to build it. The problem is the serious name conflicts if one needs to use the master Windows header file windows.h :
Thanks for the sample, I managed to build it. The problem is the serious name conflicts if one needs to use the master Windows header file windows.h :
Code Select
Building raylibDemo.obj.
E:\PellesC\raylibDemo\raylib.h(260): error #2119: Redeclaration of 'Rectangle', previously declared at E:\PellesC\Include\Win\wingdi.h(3938).
E:\PellesC\raylibDemo\raylib.h(969): error #2119: Redeclaration of 'CloseWindow', previously declared at E:\PellesC\Include\Win\winuser.h(3561).
E:\PellesC\raylibDemo\raylib.h(1019): error #2119: Redeclaration of 'ShowCursor', previously declared at E:\PellesC\Include\Win\winuser.h(6875).
E:\PellesC\raylibDemo\raylib.h(1323): error #2119: Redeclaration of 'LoadImageA', previously declared at E:\PellesC\Include\Win\winuser.h(7950).
E:\PellesC\raylibDemo\raylib.h(1474): error #2119: Redeclaration of 'DrawTextA', previously declared at E:\PellesC\Include\Win\winuser.h(6099).
E:\PellesC\raylibDemo\raylib.h(1475): error #2119: Redeclaration of 'DrawTextExA', previously declared at E:\PellesC\Include\Win\winuser.h(6119).
E:\PellesC\raylibDemo\raylib.h(1649): error #2119: Redeclaration of 'PlaySoundA', previously declared at E:\PellesC\Include\Win\playsoundapi.h(64).
*** Error code: 1 ***
Done.
#73
Graphics programming / Re: raylib 5.5 + PellesC v13.0...
Last post by TimoVJL - March 04, 2026, 05:19:10 PMThose libraries needs a RAD environment too to survive.
Just think what happened to Borland RADs.
Small programs are easy to develop with basic Win32 GUI.
TLPeView have a bit an experiment GUI, that many don't like it.
But with free source, people can make a basic GUI too or what ever they want.
Only internal functions are important, as those needs improvements.
Like resource section handling.
TLPEView is a just blackbox clone of Wayne J. Radburn excellent PEView for 32-bit files.
Wayne have full TLPEView sources how checking binary parsers was made for x64 too.
Just think what happened to Borland RADs.
Small programs are easy to develop with basic Win32 GUI.
TLPeView have a bit an experiment GUI, that many don't like it.
But with free source, people can make a basic GUI too or what ever they want.
Only internal functions are important, as those needs improvements.
Like resource section handling.
TLPEView is a just blackbox clone of Wayne J. Radburn excellent PEView for 32-bit files.
Wayne have full TLPEView sources how checking binary parsers was made for x64 too.
#74
Graphics programming / raylib 5.5 + PellesC v13.00.9 ...
Last post by rweidner - March 04, 2026, 06:24:32 AMraylib 5.5 + PellesC v13.00.9 Tutorial
Hello World using precompiled raylib binaries (Windows, 32-bit)
What we are using in this tutorial (important)
For this tutorial, we are using this exact raylib package:
- `raylib-5.5_win32_msvc16.zip`
Notes:
- `5.5` = raylib version
- `win32` = 32-bit build
- `msvc16` = compiled with Microsoft Visual Studio toolchain
At the time this tutorial was written, this is the version/package tested for these steps.
Step 1 - Go to the raylib release page
Open the official raylib release page in your browser:
https://github.com/raysan5/raylib/releases
Find the release that contains this asset:
- `raylib-5.5_win32_msvc16.zip`
(For this tutorial, we are using the 5.5 release page.)
https://github.com/raysan5/raylib/releases/tag/5.5
Step 2 - Download the exact zip file
Download this file:
- `raylib-5.5_win32_msvc16.zip`
The file is listed near the bottom of the release page assets.
Note:
- Other precompiled packages/versions may also work.
- This tutorial was only tested with the package listed above.
Step 3 - Create a clean third-party folder (recommended)
If you do not already have a place to keep third-party DLLs/libs/headers, this works well:
- `C:\dev\3rdparty\raylib\`
For this tutorial, I assume this is where you put the files.
Step 4 - Extract the zip into a versioned folder
Extract `raylib-5.5_win32_msvc16.zip` into a versioned folder, for example:
- `C:\dev\3rdparty\raylib\raylib-5.5\`
Tip:
- Avoid accidental double nesting like:
- `C:\dev\3rdparty\raylib\raylib-5.5\raylib-5.5\...`
Step 5 - Create a project in PellesC IDE
For this example, create a Win32 Console Program named `raylib_pellesc_hello` in:
- `C:\dev\`
Create a `main.c` file with the following contents:
#include "raylib.h"
int main(void)
{
InitWindow(800, 450, "raylib hello");
SetTargetFPS(60);
while (!WindowShouldClose())
{
BeginDrawing();
ClearBackground(RAYWHITE);
DrawText("Hello, raylib!", 190, 200, 40, BLACK);
EndDrawing();
}
CloseWindow();
return 0;
}
Step 6 - Configure the project
Go to:
`Project -> Project Options`
Compiler
Click on `Compiler`:
* Change C Standard to `C17`
* Enable `Microsoft Extensions`
* Click on `Compiler -> Code Generation`
* Change Default Calling Convention to `__cdecl`
Folders
Click `General -> Folders`
Notice the dropdown next to `Type` (it may default to `Libraries`).
With `Type = Libraries`, add:
`C:\dev\3rdparty\raylib\raylib-5.5\lib`
Change dropdown to `Includes`, then add:
`C:\dev\3rdparty\raylib\raylib-5.5\include`
Linker
Click on `Linker`
Under `Library and object files`, include:
`kernel32.lib advapi32.lib delayimp.lib raylibdll.lib opengl32.lib gdi32.lib winmm.lib user32.lib shell32.lib`
Important:
Repeat Step 6 for each build target you plan to use (`Debug` / `Release`).
Step 7 - Build and Run
Build and run using PellesC.
- Copy the raylib.dll found in C:\dev\3rdparty\raylib\raylib-5.5\lib to the root of the project. The exe built by the compiler should reside next to the copied dll.
- `ESC` will close the program.
If everything is configured correctly, you should see a raylib window with:
`Hello, raylib!`
Common Problems with Solutions
Build works but program will not start):
Because this tutorial links against `raylibdll.lib`, you will also need `raylib.dll` available at runtime. Copy `raylib.dll` into the same folder as your compiled `.exe`
Several compile-time errors about the redeclaration of previously declared functions.
This guide was written for Win32 console-based programming. Your project is almost certainly configured as a Win32 GUI program. The problem is windows.h and raylib.h can't be included in the same file. These are two solutions:
Tried to compile but got errors about enums
This error can pop up:
C:\SDK\raylib-5.5\include\raylib.h(210): error #2002: Invalid combination of 'enum' and 'bool'.
The fastest solution is make sure you change the C Standard option of the compiler to `C17`. (See Step 6 above) Slightly more info here: https://forum.pellesc.de/index.php?msg=42018
Unresolved externals like _InitWindow@12
This is a calling convention mismatch. Adjust the calling convention to __cdecl. (See step 6 above.)
Final Note
Let me know if I missed anything and I will update the steps.
Hello World using precompiled raylib binaries (Windows, 32-bit)
What we are using in this tutorial (important)
For this tutorial, we are using this exact raylib package:
- `raylib-5.5_win32_msvc16.zip`
Notes:
- `5.5` = raylib version
- `win32` = 32-bit build
- `msvc16` = compiled with Microsoft Visual Studio toolchain
At the time this tutorial was written, this is the version/package tested for these steps.
Step 1 - Go to the raylib release page
Open the official raylib release page in your browser:
https://github.com/raysan5/raylib/releases
Find the release that contains this asset:
- `raylib-5.5_win32_msvc16.zip`
(For this tutorial, we are using the 5.5 release page.)
https://github.com/raysan5/raylib/releases/tag/5.5
Step 2 - Download the exact zip file
Download this file:
- `raylib-5.5_win32_msvc16.zip`
The file is listed near the bottom of the release page assets.
Note:
- Other precompiled packages/versions may also work.
- This tutorial was only tested with the package listed above.
Step 3 - Create a clean third-party folder (recommended)
If you do not already have a place to keep third-party DLLs/libs/headers, this works well:
- `C:\dev\3rdparty\raylib\`
For this tutorial, I assume this is where you put the files.
Step 4 - Extract the zip into a versioned folder
Extract `raylib-5.5_win32_msvc16.zip` into a versioned folder, for example:
- `C:\dev\3rdparty\raylib\raylib-5.5\`
Tip:
- Avoid accidental double nesting like:
- `C:\dev\3rdparty\raylib\raylib-5.5\raylib-5.5\...`
Step 5 - Create a project in PellesC IDE
For this example, create a Win32 Console Program named `raylib_pellesc_hello` in:
- `C:\dev\`
Create a `main.c` file with the following contents:
#include "raylib.h"
int main(void)
{
InitWindow(800, 450, "raylib hello");
SetTargetFPS(60);
while (!WindowShouldClose())
{
BeginDrawing();
ClearBackground(RAYWHITE);
DrawText("Hello, raylib!", 190, 200, 40, BLACK);
EndDrawing();
}
CloseWindow();
return 0;
}
Step 6 - Configure the project
Go to:
`Project -> Project Options`
Compiler
Click on `Compiler`:
* Change C Standard to `C17`
* Enable `Microsoft Extensions`
* Click on `Compiler -> Code Generation`
* Change Default Calling Convention to `__cdecl`
Folders
Click `General -> Folders`
Notice the dropdown next to `Type` (it may default to `Libraries`).
With `Type = Libraries`, add:
`C:\dev\3rdparty\raylib\raylib-5.5\lib`
Change dropdown to `Includes`, then add:
`C:\dev\3rdparty\raylib\raylib-5.5\include`
Linker
Click on `Linker`
Under `Library and object files`, include:
`kernel32.lib advapi32.lib delayimp.lib raylibdll.lib opengl32.lib gdi32.lib winmm.lib user32.lib shell32.lib`
Important:
Repeat Step 6 for each build target you plan to use (`Debug` / `Release`).
Step 7 - Build and Run
Build and run using PellesC.
- Copy the raylib.dll found in C:\dev\3rdparty\raylib\raylib-5.5\lib to the root of the project. The exe built by the compiler should reside next to the copied dll.
- `ESC` will close the program.
If everything is configured correctly, you should see a raylib window with:
`Hello, raylib!`
Common Problems with Solutions
Build works but program will not start):
Because this tutorial links against `raylibdll.lib`, you will also need `raylib.dll` available at runtime. Copy `raylib.dll` into the same folder as your compiled `.exe`
Several compile-time errors about the redeclaration of previously declared functions.
This guide was written for Win32 console-based programming. Your project is almost certainly configured as a Win32 GUI program. The problem is windows.h and raylib.h can't be included in the same file. These are two solutions:
Tried to compile but got errors about enums
This error can pop up:
C:\SDK\raylib-5.5\include\raylib.h(210): error #2002: Invalid combination of 'enum' and 'bool'.
The fastest solution is make sure you change the C Standard option of the compiler to `C17`. (See Step 6 above) Slightly more info here: https://forum.pellesc.de/index.php?msg=42018
Unresolved externals like _InitWindow@12
This is a calling convention mismatch. Adjust the calling convention to __cdecl. (See step 6 above.)
Final Note
Let me know if I missed anything and I will update the steps.
#75
General discussion / Re: Compiling using pomake
Last post by rweidner - March 03, 2026, 11:50:36 PMIt's all good. No offense taken. Sometimes I use a couple of tiny .bat files for building. These are 2 of them.
build_debug.bat
===============
@echo off
call "%~dp0env_pelles32.bat"
cd /d "%~dp0"
"C:\Program Files\PellesC\Bin\pomake.exe" /F "RaylibWin32.ppj" POC_PROJECT_MODE=Debug
env_pelles32.bat
================
@echo off
REM Sets PellesC environment for x86 builds.
call "C:\Program Files\PellesC\Bin\povars32.bat"
build_debug.bat
===============
@echo off
call "%~dp0env_pelles32.bat"
cd /d "%~dp0"
"C:\Program Files\PellesC\Bin\pomake.exe" /F "RaylibWin32.ppj" POC_PROJECT_MODE=Debug
env_pelles32.bat
================
@echo off
REM Sets PellesC environment for x86 builds.
call "C:\Program Files\PellesC\Bin\povars32.bat"
#76
General discussion / Re: Compiling using pomake
Last post by John Z - March 03, 2026, 10:34:17 PMI see. No offense meant, can't be too careful these days.
Removing my prior post.
Regards,
John Z
I don't use pomake but I'm finishing up an IDE Add-In that when called creates one batch file that does the entire build process...just for fun - -
cheers,
Removing my prior post.
Regards,
John Z
I don't use pomake but I'm finishing up an IDE Add-In that when called creates one batch file that does the entire build process...just for fun - -
cheers,
#77
General discussion / Re: Compiling using pomake
Last post by TimoVJL - March 03, 2026, 10:21:10 PM #78
General discussion / Re: Compiling using pomake
Last post by rweidner - March 03, 2026, 10:10:16 PMThe reason I use the command line and pomake is because I also use a separate IDE from PellesC. I use PellesC IDE too. But sometimes I prefer something else.
No, I'm not a recruiter. In this context I'm just a dev that likes C and PellesC.
When I search my name, I see that none of my posts show up. What does show up are a few conversations about my posts. Other users seemed to get some value from at least a few of them. Maybe I'll make a few new ones to rebuild my street cred? My project today is PellesC + Raylib. I built a template for that type of project. I'll share that.
No, I'm not a recruiter. In this context I'm just a dev that likes C and PellesC.
When I search my name, I see that none of my posts show up. What does show up are a few conversations about my posts. Other users seemed to get some value from at least a few of them. Maybe I'll make a few new ones to rebuild my street cred? My project today is PellesC + Raylib. I built a template for that type of project. I'll share that.
#79
General discussion / Re: Compiling using pomake
Last post by rweidner - March 03, 2026, 09:51:50 PMThis isn't my first post. There are still a few posts around.
I wrote a GTK+ PellesC post back in the day.
I wrote a MySQL + PellesC post too.
I was certain I wrote a SDL + PellesC post at some point in the past. But I can't seem to find that one now.
I don't mean to sound like a reporter. Just trying to start a conversation. (aka General Discussion)
I wrote a GTK+ PellesC post back in the day.
I wrote a MySQL + PellesC post too.
I was certain I wrote a SDL + PellesC post at some point in the past. But I can't seem to find that one now.
I don't mean to sound like a reporter. Just trying to start a conversation. (aka General Discussion)
#80
General discussion / Compiling using pomake
Last post by rweidner - March 03, 2026, 05:27:26 PMI noticed a post recently where someone was trying to compile using pomake. I didn't attempt to compile his examples. Others looked and determined the issue was user error. But the whole thread got me thinking. Why compile from the command line?
I can explain why I use that approach. It may seem unusual to some, but it works for me. I let PellesC manage my *.ppj files, while I sometimes use a different IDE for coding. Project management and debugging stay in PellesC, and pomake handles the builds.
So, my questions are:
I can explain why I use that approach. It may seem unusual to some, but it works for me. I let PellesC manage my *.ppj files, while I sometimes use a different IDE for coding. Project management and debugging stay in PellesC, and pomake handles the builds.
So, my questions are:
- What workflow issue are you personally trying to solve if you're compiling from the command line?
- What challenges does your "outside the box (IDE)" create, if any?
- Did you solve those challenges? If so, how?