Which compiler to use to make plugins

[Si]

My old machine went belly up at Xmas and I've just got a new machine up and running.

But do I try and find my old VC++6 CD's and service packs or should I just use the VC++ 2005 Express freebie to get back into the plugin business :confused:

regards

Simon

[tsp]

you can use both.

[Richard Berg]

I don't see any reason to use VC6 (ick).

[mg262]

VC6 had a profiler...

[tsp]

AMD's CodeAnalyst (http://developer.amd.com/cawin.aspx) is free to use (and the timer based profiling does work on an intel processor).

[Prettz]

VC++ 6 isn't so great at producing the fastest code possible, especially if you don't intend to optimize your code for the Pentium Pro. I've heard the VC++ .NET optimizing compiler is better, but I haven't looked at it yet.

[Si]

Well, I downloaded VC++ Studio Express and downloaded the Platform SDK.

Loaded in an old VirtualDub plugin and tried to compile it - errors all over.

Then found out I had to explicity include the Platform SDK in my paths.

Still got errors - tried everything - searched T'internet- got nowhere - then redid my entries for include paths for SDK - worked :stupid: (Tip - don't type in things - use browse and let the computer type it in for you)

VirtualDub plugin worked - time to move onto Avisynth.

Tried a test version of Viewfields - tried compiling and running it in Debug mod and calling VirtualDubMod (As I used to do) to test out scripts - kept getting a strange error about not being able to recognise .avs files ????

Then it dawned on me - I hadn't actually installed Avisynth :rolleyes:

So after doing that and a few more errors (my old test avisynth project wasn't 2.5 compatible) I finally got it working - yippee!!!

One more question - don't I have to make the compliler set the DLL to multilthreaded - how do I do that (or was that a VirtualDub necessity?) - I'm getting too old for this game ;)

regards

Simon

[foxyshadis]

VS2005 doesn't support single-threaded anymore, so nope. :p

Today's been my day at it too, I compiled vdub and avisynth (don't even bother with the latter unless you have a couple hours to fix scoping errors and hunt down libraries to recompile). Neither worked entirely, but it's getting there. And found the PSDK has a few bugs as well, bad return types in string.h. >.>

[jmac698]

foxyshadis: haha, you are really inspiring me here, to write my own filters ;)

[foxyshadis]

Oh, all the filters I've tried worked fine (though one or two needed some scope fixes), it's avisynth core itself that has a lot of VC6 legacy code left in it. Plugins are simple enough that they don't have all those dependencies and tons of code (except beasts like tivtc).

[Fizick]

SI,
Do you use old VC6 IDE with new vc2005 compiler, right?

[Si]

No - I've just opened up an old VC6 project and recompiled it using VC2005

regards

Simon

[Fizick]

Can VC2005 Express open old VC6 project *.DSW files?

[tsp]

yes but it can't save dsw files

[dimzon]

btw
you can use this
http://msdn.microsoft.com/visualc/vctoolkit2003/ -it's FREE Optimizing C++ compiler & linker as shiped with vs2003 PRO
+ this
http://www.codeblocks.org/