The dreaded Visual Studio? Visual Studio is dreaded? Why? (Well, okay, I guess the C++11 support is somewhat lacking...)
After spending a couple minutes looking, I found a couple of odd things:
1) People still use RAR files?
2) Of the files Visual Studio generates, the only files vital to building the project are the .sln and .vcproj. The rest -- .sdf, the intellisense database; .suo, the solution options (??); the .vcxproj.user -- aren't needed, should be deleted.
3) Do not distribute the Debug versions of your executable. The debug versions of the C runtime library are intended for development only, not for deployment.
4) Multiple copies of the res directory?
5) (Nitpick) Your vcproj assumes I have SDL installed in C:\SDL-1.2.5 -- I actually have it installed in C:\bin\sdk\SDL\1.2.5. It doesn't really matter as long as your project links to an SDL.lib, and I have properly set up the appropriate directory.
I'll take a much thorough look inside your project later...
Dreaded because I do not like how VS handles properties for different projects. Give me makefiles any time of the day. Perhaps I am just used to the Unix way of dealing with these. I do use VS at most places I work though.
Well yes it's true that I did some tests at some point in time and Zip files were superior in pretty much every category against rar files. I guess I'm used to WinRar. I would have tarred it if I was on Unix.
You are right, sorry about that I was lazy.
Essentially the res directory was unique, but I copied it in the .exe for a quick run for anyone who was interesting in trying it out. I think I left the .bmp too for no reason. Packaging again, my fault
I normally use environment variables(Such as creating SDL_DIR="path"), It would have fixed your problem per se, but it would have facilitated the integration.
@arrgh, yes indeed, I mentioned the loop earlier my fault, thanks for pointing out it's importance.
Thanks for the input.