Recent posts

#31

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

Last post by Vortex - March 17, 2026, 09:37:26 PM

I think processors dating back to 2012\2013 are supporting the movbe instruction.

#32

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

Last post by John Z - March 17, 2026, 08:59:06 PM

Tested on Window 7 Pro, DELL 64 bit (still get security updates)

Install seemed ok, however poide would not start even enough to show a window.
Didn't see it running in the background either.
poview worked.

DEL optiplex 780 Intel Core Duo E8400 release date 2008

John Z

Update: Tested on Win 11 Home 24H2 HP, was successful, installed and built vcardz_i program fine.

#33

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

Last post by TimoVJL - March 17, 2026, 12:37:16 PM

Hopefully users test new version and don't wait release version.
I try to test Windows 7 with new version, but every PC's CPUs are problem.
Windows 10 and 11 test PCs should not having any problems.
Pelles C support testing other versions with -x -xml poide commandline options.

#34

General discussion / Re: Compiling using pomake

Last post by John Z - March 17, 2026, 09:50:31 AM

Yes, main.c is in a different directory. I have a reason for it. It is just not a great reason. LOL.

Got it - a 'works for me situation'  Hierarchical and more structured.

Thanks,
John Z

#35

Bug reports / Creating resource with manifes...

Last post by PaoloC13 - March 17, 2026, 12:07:33 AM

Start a new project >
 Win64 Program (EXE) | Name: Test >
  Open >
   Filename: main.c >
    Add file to project >
     Filename: main.c >
      Open >
       Build >

[Ouput]
Project build started
Project build ended successfully

File >
 New >
  Resources (Untitled) >
   New >
    Manifest >
     Save >
      Filename: resources >
       Save >

"Do you want to add the file 'resource.rc' to the current project?" >
 Yes

[Ouput]
Document saved: C:\Documents\Test\resources.rc

Build >
 ...Freezed with spinning wheel

Version: 13.00.9
Windows 11

#36

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

Last post by Vortex - March 16, 2026, 09:27:38 PM

Here is the 64-bit version :

Code Select Expand

include     movbeCheck.inc

.data

m1          db 'The processor does not support the instruction movbe.',0
m2          db 'The processor supports the instruction movbe.',0
StrTable    dq OFFSET m1,OFFSET m2

.code

start:

    sub     rsp,8+4*8
    call    main
    invoke  ExitProcess,0

main PROC PARMAREA=4*SIZEOF QWORD

LOCAL _rax:QWORD

    xor     rax,rax
    mov     _rax,rax
   
    mov     rax,1
    cpuid

    bt      rcx,22
    mov     rax,_rax
    adc     rax,0

    mov     rdx,OFFSET StrTable
    lea     rcx,[rdx+8*rax]

    invoke  printf,QWORD PTR [rcx]
    ret   

main ENDP

END start


#37

Assembly discussions / Verifying the support of the i...

Last post by Vortex - March 16, 2026, 08:45:29 PM

Hello,

To check if your processor supports the instruction movbe :

Code Select Expand

include     movbeCheck.inc

.data

m1          db 'The processor does not support the instruction movbe.',0
m2          db 'The processor supports the instruction movbe.',0
StrTable    dd OFFSET m1,OFFSET m2

.code

start:

    xor     eax,eax
    push    eax
   
    mov     eax,1
    cpuid

    bt      ecx,22
    pop     eax
    adc     eax,eax

    invoke  printf,DWORD PTR [StrTable+4*eax]
    invoke  ExitProcess,0

END start


#38

General discussion / Re: Compiling using pomake

Last post by TimoVJL - March 16, 2026, 08:09:44 PM

How project works with version 14 rc1 ?

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

#39

General discussion / Re: Compiling using pomake

Last post by rweidner - March 16, 2026, 07:52:25 PM

Yes, main.c is in a different directory. I have a reason for it. It is just not a great reason. LOL.

My personal convention is to keep the program entry point next to the project file. The goal is simple: if I come back to this code months or years later, I do not want to hunt for the entry point. I also typically build the .exe next to the project file while I am debugging, so having main.c at the top level feels like it belongs with the build/run artifacts.

So for me, the top-level folder is "project management." Finding the entry point is barely in that domain, but it is in it enough that this pattern stuck.

Everything else that is "real code" lives under src\ (and headers under src\include\). Assets, deps, and notes get their own folders.

This layout is pretty typical for me:

Code Select Expand

C:\dev\XecronixEngine\FBIPursuit>tree /F
Folder PATH listing
Volume serial number is 73AB-A1AE
C:.
│   env_pelles32.bat
│   FBIPursuit.exe
│   FBIPursuit.geany
│   FBIPursuit.tags
│   main.c
│   project.bat
│   raylib.dll
│   RaylibWin32.ppj
│   RaylibWin32.ppx
│   RaylibWin32.tag
│   README.md
│   tags.bat
│
├───assets
│   │   scores
│   │
│   └───level1
│           astronaut12-energy-gaming-electro-trap-301124.mp3
│           astronaut12-ultimate-gaming-soundtrack-for-legends_astronaut-272122.mp3
│           astronaut12-victory-awaits-in-the-gaming-universe_astronaut-265184.mp3
│           baddie1.pdn
│           baddie1.png
│           civ1.pdn
│           civ1.png
│           click.wav
│           click_heavy.wav
│           damage.wav
│           explode.wav
│           fassounds-level-up-energetic-gaming-rock-music-251284.mp3
│           hero.png
│           hit.wav
│           hitslab-retro-retro-synthwave-gaming-music-270173.mp3
│           level.map
│           mroneilovealot-neon-overdrive-cyberpunk-gaming-edm-415723.mp3
│           sapan4-edm-gaming-music-335408.mp3
│           shot.wav
│           shots.png
│           song1.mp3
│           stereo-complete-in-dash.png
│           tiles.png
│
├───deps
│   │   MANIFEST.txt
│   │
│   ├───include
│   │       raylib.h
│   │       raymath.h
│   │       rlgl.h
│   │
│   └───lib
│           raylib.dll
│           raylib.lib
│           raylibdll.lib
│
├───output
│       actor.obj
│       actor_manager.obj
│       actor_templates.obj
│       game_sim.obj
│       gfx_manager.obj
│       high_score_sim.obj
│       main.obj
│       pause_sim.obj
│       settings_sim.obj
│       sfx_manager.obj
│       start_sim.obj
│       xx_input.obj
│
├───project_notes
│   │   game_rules.txt
│   │
│   ├───designIdeas
│   │       initialRoughEngineIdea.txt
│   │
│   └───milestones
│           milestones.txt
│           milestones_fbi_pursuit_v1_2026_02_27.md
│
└───src
    │   actor.c
    │   actor_manager.c
    │   actor_templates.c
    │   game_sim.c
    │   gfx_manager.c
    │   high_score_sim.c
    │   pause_sim.c
    │   settings_sim.c
    │   sfx_manager.c
    │   start_sim.c
    │   xx_input.c
    │
    └───include
            actor.h
            actor_manager.h
            actor_templates.h
            game_sim.h
            gfx_manager.h
            high_score_sim.h
            pause_sim.h
            settings_sim.h
            sfx_manager.h
            start_sim.h
            xx_conf.h
            xx_input.h
            xx_types.h



#40

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

Last post by Vortex - March 16, 2026, 01:22:18 PM

To check if your processor supports MOVBE, run Coreinfo on the command prompt :

Code Select Expand

Coreinfo64.exe -f
Check the output of the tool to see if MOVBE is supported :

Code Select Expand

MOVBE           *       Supports MOVBE instruction
https://learn.microsoft.com/en-us/sysinternals/downloads/coreinfo