Hi again Jesse,
Did you download an archive (tarball or zip probably) of SDL from
revision control? You should probably check out a “live” copy so that
you have an easier time applying patches as they come in. You’re
building from cutting-edge source code, and I suspect there are not a
lot of Visual Studio users out there doing the same as you. As such,
however, we do appreciate your effort, as it benefits us all to have
someone using it and telling us what works and what doesn’t, but what
you should know about your quest is this:
You should be able to troubleshoot basic compiler problems and follow
updates to revision control yourself. Anyone who is helping you
without the benefit of access to the exact revision(s) of SDL and the
version+variant of MSVS you’re working with is mostly taking shots in
the dark which would be better handled by you since you actually have
access to these things.
I hope this isn’t very discouraging to you! But you can’t just remove
a source file from a particular revision which it was clearly included
in and necessarily expect it to start working.
Download a Subversion client for Windows and learn a little bit about it:
http://tortoisesvn.tigris.org/
Check out a revision controlled copy of SDL:
http://svn.libsdl.org/trunk/SDL/
Try to keep in-the-know with the changes that are being made to the
SVN repository. Your subversion client will make it relatively easy
for you to adjust your local copy of SDL to match any numbered
revision in the repository (if you thought you had to remove a file
because it had be been removed in a more recent revision, for
instance, it is easy to update to a specific revision, or just the
most recent revision.) It can also inspect the changes that have been
made to a file over time, and with those changes, the messages left by
the authors of the changes. Also feel free to play around with SDL’s
ViewVC interface:
http://www.libsdl.org/cgi/viewvc.cgi/trunk/SDL/
All these things should help you get a better grasp on how to
troubleshoot the problems you’re experiencing (although it’s not
entirely unlikely that the latest SVN revision will just work if
someone has gotten around to it.)
More to follow…On Tue, Dec 30, 2008 at 8:10 AM, Jesse P. wrote:
When I remove SDL_fill.c from project
I get 18 more errors:
[snip]
1>SDL_compat.obj : error LNK2019: unresolved external symbol …
1>SDL_nullrender.obj : error LNK2001: unresolved external symbol …
1>SDL_renderer_sw.obj : error LNK2001: unresolved external symbol …
[snip]
It looks like you’ve removed the file that – in your copy of SDL –
implements those functions. So now when it comes to time to link your
project, those functions are missing. Removing the file was not
precisely the right thing to do.
According to the revision log (URL below) Sam updated the MSVS project
file on Christmas (what a trooper!) with a very positive log message:
“Updated to build on Windows.”
http://www.libsdl.org/cgi/viewvc.cgi/trunk/SDL/VisualC/SDL/SDL.vcproj?r1=4095&r2=4272
Now it looks like maybe you’ve downloaded an archive of the repository
since he made that change, but according to this diff from revision
control, you haven’t been building with that SDL/VisualC/SDL.vcproj
file!
[from]
http://www.libsdl.org/cgi/viewvc.cgi/trunk/SDL/VisualC/SDL/SDL.vcproj?r1=4095&r2=4272
Ok I hope I’ve shown you a good direction to go in the future. Good luck!
–
http://codebad.com/