-
Notifications
You must be signed in to change notification settings - Fork 11
error: no member named 'stdio' in 'union SDL_RWops:: while building #5
Comments
cc @Daft-Freak @juj |
It looks like the build is finding the SDL 1.3 headers ( Also, looks that README file needs some updating... |
How do I specify the version of SDL for the build? |
IIRC "-s USE_SDL=2" |
How do I use I mean, in the docs, the use of such option is supplied to the compiler call Do I have to manually modify the Makefile? |
If there's an installed SDL2 build at |
The building of SDL2 went like charm actually, I am struggling to get SDL2_Image to build.. I do supply the built version of SDL2 to the |
Did you |
Yes, I did. However, one thing I noticed when I was ran
And I noticed that there is no bin directory in SDL-emscripten. |
Make sure |
And where is that? |
The path passed as |
Since it was not specified in To avoid ambiguity I have re-ran I apologize for the inconvenience, |
Ah, didn't notice that the SDL2 docs don't mention specifying a prefix. I don't think the instructions for building SDL2_image have been updated since the initial port. I'll go and update that now. |
I definitely had some trouble getting this working on my system, which happens to be OSX... I didn't install any libs though (and don't plan to since where would they go anyway?). In any case here is what worked for me. There is some more scripting before this to copy all needed files into
It takes a few tries... since it doesn't have the auto cloned ports until the first run, so after the first failure I apply the hacks below. I can't quite understand why when I've specified
So the strange things... my project won't build because the header files are not found, so I'm already needing to specify the paths to the necessary header files (which means I already have my own copy of emscripten_ports locally )... but when it tries to find the headers to build SDL_Image the ones I specified are ignored. I understand that there is probably a way around this using a prefix path and actually installing the headers there. At first I was trying to not use either of the I wonder about the possibility of one of these:
I'm using this version of emsdk: I would post a link to my WASM build, but thats not the purpose of this post, just trying to help anyone who is stuck and possibly figure out why I had so much trouble and spend so much time trying to figure this out. Thanks! |
The |
Hello,
so I followed the specified steps to build SDL2_image, I did as
README-emscripten.txt
specified.the command:
has succeeded, however when I run
the following error promps out:
I appreciate the help.
The text was updated successfully, but these errors were encountered: