Why is msvcr70.dll needed when using VC7 and the latest snapshot?

[dvd2svcd]

Well, the entire question is in subject. I just downloaded the latest Snapshot of your CVS and compiled it using VC7 and now it seems that Avisynth needs msvcr70.dll when distributed, is that on purpose?

Oh and one other minor thing, the dsw file is gone and when loading the dsp file in VC6 it says that the makefile is created by another version and can't be used (or something to that effect), again, is that on purpose?

[vlad59]

It's strange I have no problem loading the DSP in my VS6. I will make checkout and retry !

[sh0dan]

VC7 probably links to it's own runtime, instead of the older. Don't know what you can do about it. I think Avery had the same problems with Vdub!?!

Regarding VC6 - are you sure VC7 hasn't modified it? Have you tried a clean CVS snapshot?

The current binaries are compiled using VC6 SP5, since it has the same code generation as VC7 - so there should be no advantage of compiling with vc7.

[dvd2svcd]

You're right I just downloaded the CVS here at work and here VC6 has no problem loading the DSP file, so disregard that. But the thing about msvcr70.dll and VC7 still stands I think.

EDIT:
I know, I'm a pain, but if I don't remove this (using VC6):

Ln 225 in source.cpp
strcat(foo, itoa(GetLastError(), bar, 10));

I get this error when building:

Linking...
xilink6: executing 'C:\PROGRA~1\MICROS~4\VC98\Bin\link.exe'
Creating library Profile/avisynth.lib and object Profile/avisynth.exp
source.obj : error LNK2001: unresolved external symbol __imp__itoa
Profile/avisynth.dll : fatal error LNK1120: 1 unresolved externals
Error executing xilink6.exe.

EDIT AGAIN:

The above problem can be fixed by adding this in the source.cpp :

#include <stdlib.h>

#ifdef _MSC_VER
#define itoa(a,b,c) _itoa(a,b,c)
#endif

[sh0dan]

What's "xilink6.exe"? - doesn't recall ever using this - just plain old link.exe.

What if you change to the Release or Debug builds - it's been ages since I tried to compile using "Profile" - I don't even know what it's for. :rolleyes:

Regarding msvcr70.dll, it may just be the cost of using vc7 - ffdshow had the same problem, when someone (can't remember who, sorry) compiled it using VC7.

[vlad59]

xilink comes from the Intel Compiler. I assume dvd2svcd use it and it has some incompatibility with the standard MS one.

Regarding msvcr70.dll, it should be possible to statically link it if it's really a problem (it costs some Ko of course).

[dvd2svcd]

Hmm, that's weird, I was sure that I had disabled the Intel Compiler/Linker. Better have a second look. Thanks :)