Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: Entry Point not found  (Read 1290 times)

0 Members and 1 Guest are viewing this topic.

topfpflanze

  • Newbie
  • *
  • Posts: 7
    • View Profile
    • Email
Entry Point not found
« on: June 21, 2016, 04:46:22 pm »
Hey,
after being forced to move from Windows 7 to Windows 10 recently, I wanted to work on one of my older C++ projects using SFML. I downloaded the latest version and the corresponding MinGW package, setup Eclipse and ran a testing make command. So far so good, everything seemed to work, the program compiled without any errors. When I wanted to run the executable though I was getting "Entry Point not found" messages for all the SFML modules I used (System, Graphics, Audio). I searched up the issue a bit and found that this normally happens when you link to library files to compile the program that don't match the dll files. Weird, since i just did a fresh download but I thought I'd try it again. Cleaned everything up, did a fresh MinGW and SFML Download. Still the same error. I then downloaded the SFML source files and built it with the latest MinGW version and then built my program with that version too, just for checking if it might be a compiler problem after all. However I still got the same issue and I'm kinda clueless now.
Might that be a problem with Windows 10 or is there something else I haven't considered?
« Last Edit: June 21, 2016, 04:51:53 pm by topfpflanze »
#define true false

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 11030
    • View Profile
    • development blog
    • Email
AW: Entry Point not found
« Reply #1 on: June 21, 2016, 08:37:31 pm »
You might have old DLLs next to your exe.
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

topfpflanze

  • Newbie
  • *
  • Posts: 7
    • View Profile
    • Email
Re: Entry Point not found
« Reply #2 on: June 22, 2016, 04:54:13 pm »
I didn'T have any dlls next to the exe however it seems it has been a fault with MinGW rather than SFML since it worked when I rearranged the MinGW folder to be the first one in the PATH System Variable
#define true false

 

anything