AviSynth 2.6 move to VC2005 Express.

[sh0dan]

I think it's about time that AviSynth moved off an 8 year old platform, so I have ported AviSynth 2.6 to VC++ 8 Express.

This makes it possible for you to compile and contribute to AviSynth 2.6 with Microsofts free Express Edition. It might also fix some of the bad compiler issues Ian has spent so much time tracking down.

If nobody have any serious objections, I'll commit the code to the 2.6 branch.

[Guest]

Can VC++ 8 Express co-exist with earlier versions on one's PC, such as VC++ 6?

[berrinam]

What libraries are required, since VC2005 Express doesn't come with any at all? MS Platform SDK, perhaps?

[Wilbert]

Originally Posted by neuron2

Can VC++ 8 Express co-exist with earlier versions on one's PC, such as VC++ 6?

15. Will the Visual Studio Express Editions install side-by-side with other versions of Visual Studio?

Yes, side-by-side compatibility with other versions of Visual Studio has been tested.

from the FAQ: http://msdn.microsoft.com/vstudio/ex...q/default.aspx

Originally Posted by berrinam

What libraries are required, since VC2005 Express doesn't come with any at all? MS Platform SDK, perhaps?

They say you will want to install PSDK, so i guess that means yes

http://msdn.microsoft.com/vstudio/ex...alc/usingpsdk/


I guess you need to uninstall .NET Framework 1.1 or .NET Framework 2.0 first though.

installing without registering: http://forum.doom9.org/showthread.ph...161#post736161

[foxyshadis]

I didn't have to, and even the pro version needs an updated PSDK as soon as you install it. VC Express does come with basic header files, but I'm not sure if it's missing libraries like openMP.

[IanB]

Call me a ludite but I will still be working with good ol' VC6! I see no reason to break support for that.

[sh0dan]

Can VC++ 8 Express co-exist with earlier versions on one's PC

Yes - works very nicely on my PCs. "DSW" files open in VC6, "VCPROJ" in VC7, "SLN" in VC8.

What libraries are required, since VC2005 Express

There is no MFC support in VC2005, but AviSynth doesn't use MFC, expecpt for adding the version number to the DLL. Other than that the PSDK is required for AviSynth, and DirectX for compiling the Directshow plugin. TCPDEliver needed to have some AFX-related stuff removed, but I've already done that.

@IanB:
The main change is that variables declared in a for loop will no longer work outside the for-loop scope - that will not compile in VC6. I had to recompile the Soundtouch library with VC8, but beside that nothing much besides loops had to be changed.

I see no reason to break support for that

Well, the world moves on. VC8 is free, which I think is a great thing for OS software, it's supported, and has a better compiler.

[Fizick]

How will be VC6-compiled plugin compatibility?

[foxyshadis]

Seamless, as far as I can tell, except that once in a while you have to substitute the VC6 or 7 ml.exe while assembling, or disable for loop conformance (as sh0dan mentions). For the most part every plugin I've loaded has compiled without errors on the new one.

Oh, and DXSDK isn't required at all anymore (unless you're building MPC or something), DS is all in PSDK, although the version of PSDK that comes with 2005Pro is so dated that it doesn't include DirectShow at all.

[IanB]

Originally Posted by sh0dan

The main change is that variables declared in a for loop will no longer work outside the for-loop scope - that will not compile in VC6.

It won't compile only if you don't fix the code correctly.

[IanB]

Sh0dan, you are really pushing it here. Yes, I think it is a good idea to feed the source through the new compiler and amend the code to clean up all the warning/errors in preparation. And we should do this at the maximum winge level. And yes we should be exercising this new environment. But it does not mean that we should not be able to still develope and debug under familiar VC6. When finding and fixing insideous bugs in a major new release I really don't need the extra headache of fighting to learn a new environment.

Originally Posted by http://www.virtualdub.org/blog/pivot/entry.php?id=108

One little change that can bite you is that catch(...) no longer catches Win32 exceptions, most notably access violations.

This is a very serious problem! Do we really want to spend a lot of time reworking this, instead of getting the new core functionality written.

Note that Express does not include the Win32 resource editor, ...

This also effect the ICON as well as the REV block. It will probably be good for the soul to relearn to manuallly edit .RC files.

[foxyshadis]

Express doesn't include the resource editor but that doesn't mean you can't import from VC6/7. Odd about the other one though. (Avery has amazingly informative blogs about VS.)

[sh0dan]

@IanB: ok - never mind. Let's just keep the old VC6, then.

[IanB]

@sh0dan: - By all means checkin any syntax polishing you have worked on. Getting the source syntax cross compatible is a very important first step.

My thoughts for doing a platform change would be to do it as a null functionality change so we can do A - B cross checking. Something like develope 2.6.0 under VC6, with near as possible 2005Exp compatible syntax. Do 2.6.1 as a bug fix release + reworking of things like the *.ASM's and the try/catch(...)'s that will choke in 2005Exp. Then do 2.6.2 as an Identical 2005Exp release of 2.6.1 i.e. no new features just pure base translation.

[devaster]

where is source ???
i have checked cvs yesterday and avs26 folder is empty ...

[IanB]

It's in the regular tree as CVS branch "avisynth_2_6"

[devaster]

IanB :
when I select this CVS branch its still empty ...
Iam using a tortoise CVS for checking ...

[IanB]

Wander around the CVS Tree with a web browser to get your bearings first. The files changed specifically for 2.6 have revision stamps like 1.22.2.6 (4 part numbers)

[Wilbert]

I attached two screenshots for you. pm the relevant mods if it they forget to approve them

[devaster]

Thanx Wilbert