KVR Audio

Jimbrowski-one · Post by **Jimbrowski-one** » Tue Sep 15, 2009 5:13 pm

I would suggest - if you haven't done this already - that you make static libraries of VSTGUI, libPNG, zLib, etc... it's just one of those little things that bugged me when looking at the examples in the VST SDK. Speeds up compile time tremendously since you are generally not going to mess the internals of these.

arakula · Post by **arakula** » Wed Sep 16, 2009 7:08 am

heptapod wrote:Got it working with VstHost. Vc++ complains saying that VstHost was built without debug information, but it works anyway.

If you want that, get the Open Source variant and compile it with debug information. While it doesn't have all features of the current version, it certainly does allow to develop and debug most of a VST 2 PlugIn.

arakula · Post by **arakula** » Wed Sep 16, 2009 7:10 am

deraudrl wrote:
arakula wrote:Either use a fully qualified path for the DLL or assure that the Debug directory is the current directory.
Hmmm...can the standard macros (like 'OutPath' and 'ProjectPath') be used in that command line?

Would be worth a try.

deraudrl · Post by **deraudrl** » Wed Sep 16, 2009 3:18 pm

Jimbrowski-one wrote:I would suggest - if you haven't done this already - that you make static libraries of VSTGUI, libPNG, zLib, etc... it's just one of those little things that bugged me when looking at the examples in the VST SDK. Speeds up compile time tremendously since you are generally not going to mess the internals of these.

+1.

Note that you'll sometimes get a bunch of warnings about "vc90.pdb" being out of date or unavailable for those libraries, but AFAICT they're benign linker artifacts. (Or I need to change some obscure setting and recompile the libs. And yes, I made both debug and release versions of them.)

Setting up a nice development environment for vst