Irrlicht Engine

Does anybody have the compiled static lib?
Why isn't it included in the SDK?

Sorry to appear lazy but it would save people some time if someone has it, instead of having to figure out the compiling part, as there's always quirks.
Thanks guys! what a great engine!

If you find threads which are dead for more than half a decade you might consider creating new ones instead of trying to revive 'em ;-)

And sorry - building releases is just a lot of work as libs have to be tested. I suspect in the future we even will drop the dll as it's no longer possible to create a single dll which works with all the different VS versions (or maybe we deliver one just for latest VS version, but I haven't managed to get that one working yet on my computer...)

Oh ok thanks that's interesting, sorry for reviving the zombie.
I will delve into creating the static lib now...

@CuteAlien: I know VS writes the version number into the DLL, but I thought this was a feature of the free compilers. Surely *ahem* one can specify a target (or no target) that will allow linking with any compiler, perhaps with a non-free compiler. Microsoft must do it for the platform SDK, Nvidia has to do it for their drivers, etc.

mongoose7: No, platform sdk's are per compiler (you see for example msvcp100.dll - the 100 is the platform toolset). One can use that from any VS compiler if you have the corresponding platform toolset installed (which usually means you have the corresponding VS installed). I had switched Irrlicht all compiler solutions to Windows 7.1 SDK which is kinda an independent SDK. But has some disadvantages - first it means people have to install that SDK. Next - it's basically just platform toolset V110 with a new name. And that means - people can't use any newer compiler features (like c++11 for example) when linking to that dll. And lastly - I found no way so far having that installed at the same time as the newest VS 2015. VS2015 has a new SDK which changed a lot - and it simply doesn't seem to compile any projects anymore when one has older versions of the SDK on the system. There might be some way around it (something about paths obviously...), but I already spend a full day on it without finding a solution (it's not as simple as with Makefiles, VS hides very well from where it get's it's settings sometimes ...).

OK. I don't know how to do it, either. I link statically, so it is not a problem