You can just redefine them with a precompiler statement.

#if _MSC_VER
#define snprintf _snprintf
#define strncmp _strnicmp
#endif

Etc... This will be ignored by the linux compilers and will properly replace the functions under MSVC

MSVC
 

I think the define statements make sense short-term, to get OpenSSN up and running now. Long-term though I have concerns about patching against specific compilers. There are a lot of C/C++ compilers out there. Ideally I'd like to have a solution in place that will work on Windows, regardless of which compiler is used.

I will play openssn in Linux, but if you can port it to Windows you will enlarge your audience...

I think is more a matter of how much time you have at your disposal and how much of this time will the windows port need.

PS: i've just sent to you an outdated Spanish manual translation. :cry:

I have very little spare time this last month...

Typhoon, if you want me to upload the windows binaries to SF my username is magic-stix.

Upload access
 

I've granted the account magic-stix release file access, which should allow you to upload binaries to the mirrors. If it's not working, please let me know.

Windows version is up.

Windows version
 

Thanks!
Before announcing the new version I downloaded and tried to give it a run (I've got WINE) and I'm getting the "incorrect application configuration" message which so commonly plagues MSVC developers. Could you check to see if a DLL is missing?

This page has details on how to cover all the bases:
http://www.virtualdub.org/blog/pivot/entry.php?id=296

Hmmm. That's odd, the game works fine for me right out of the zip. Does it say which dll is missing?

OK I pulled the zip and ran it on my other windows machine and got an error. I'll look into it, i think I'm probably missing the msvc c runtime dll.

DLLs
 

No, the error doesn't say which DLLs are missing. But one of the prime characteristics of the "incorrect configuration" error is that people with MSVC installed on their machines can run the program fine, but people without MSVC cannot. It's pretty common. The list of problem DLLs is available in the link I posted.

Update: I just you beat me to a follow up post.

For some reason it keeps trying to use the debug versions of the Visual C runtime libraries, I've gone back and rebuilt openSSN and all of its dependencies but the deps seem to still want to use debug symbols... I'll poke around at it some and see if I can fix it.

OK try it now. For some reason the SDL_gfx.dll was trying to link against debug symbols for the C runtime regardless of how I built it, so I built it with static linking of deps instead. Works on both of my windows machines now.

Works A-ok here
 

The new package works a-ok here. Everything seems to be intact and i was able to run it (emulated) and play through a mission. Very nicely done, sir. I will make the appropriate announcements.

Thank you very much for your hard work.

I would definately be interested in seeing OpenSSN ported over to WindowsXP, Vista or 7. I use XP myself and the last version of OpenSSN I have works great. I have version 0.7. I just installed copies of MinGW C++ and Microsoft Visual Studio 8 for another project I'm working on. I'm trying to teach myself C++ and Visual Basic so I can port an older Visual Basic 5.5 program and finish it! :O:

ChristopherT

There's already a windows version out there, it's kinda old though...