Re: Failed to load SHCORE.DLL

Armando Alaminos Bouza <[email protected]>
Newsgroups gmane.comp.lib.sdl
Message-ID <CANR5g3ho3rGmnasjD6HcP9_uSGeWQMmbooRjKadHK=SdQm9daw@mail.gmail.com>
The only complain that I frequently have with XP is lack of support for
hardware acceleration.
So, for Windows XP you need the parachute of  SDL_RENDERER_SOFTWARE when
you call SDL_CreateRenderer()

Armando AB

On Thu, Aug 11, 2016 at 7:22 PM, Jonathan Dearborn <[email protected]>
wrote:

> As long as XP is still supported by SDL, that wouldn't solve the problem.
>
> Jonny D
>
>
> On Thursday, August 11, 2016, Jesse Palser <jessepalsermailinglists@
> gmail.com> wrote:
>
>> Umm....
>>
>> Windows XP has been dead for some time now and is buried - update to a
>> more recent Windows...
>>
>> Jesse
>>
>>
>>
>>
>> On 08/11/2016 04:18 PM, BenoitRen wrote:
>>
>> Greetings
>>
>> My SDL2 application doesn't run correctly. No window gets created, but
>> the return values don't indicate an error. If I call SDL_GetError anyway
>> and print its result, it says that SHCORE.DLL could not be found. I found
>> another message about this on this mailing list, but there was no reply.
>>
>> I'm using MinGW on Windows XP SP3, and I made sure to use the headers,
>> libraries and DLL from i686-w64-mingw32. The "w64" worries me, though. But
>> compiling with the regular includes and the libs under x86 produced an
>> error about main being defined twice.
>>
>> I've read the readme files but they didn't contain anything useful.
>>
>>
>> _______________________________________________
>> SDL mailing [email protected]://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>>
>>
>>
> _______________________________________________
> SDL mailing list
> [email protected]
> http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>
>

_______________________________________________
SDL mailing list
[email protected]
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.