It may be possible to statically link with the VC redist, in which
case shadowspawn would become standalone. The issue with doing that is
that Microsoft publishes security updates to the redist via Windows
Update, and we wouldn't get those if we were statically linked. At
that point, it would be on you, the user, to download a new version
that had the updated version included. Assuming that one of us notices
the update and remembers to compile a new version.
Another possibility would be to do the work to remove the dependency
on the VC runtime. That work may be extensive in nature - no idea.
I've added this to our issue list [1], but I have to say that I'm not
sure we'd implement this any time soon.
Sorry I can't give you a better answer, but thanks for the inquiry!
Unfortunately, I'm not enough of a C++ jockey to have that information
on the tip of my brian. Things I would wonder about include CString
and the ATL, which we use in quite a few places.
Not sure when (or if) I'll implement it, but it's nice to know what is
needed. Thanks again!
On Mon, Nov 14, 2011 at 12:58 PM, Ro Lo <rohit...@gmail.com> wrote:
> We can add 3(6) more configurations to project file
> Release-Static-XP ....
> We just need to change C++ -> Code Generation -> Runtime Library
> I do not know Git enough to give you patch file.