cannam@239: cannam@239: The Vamp Plugin SDK -- Platform Notes for Visual C++ on Windows cannam@239: =============================================================== cannam@239: cannam@239: Visual C++ Project Files cannam@239: ------------------------ cannam@239: cannam@239: Three Visual C++ project files are included with the SDK: cannam@239: cannam@239: - build/VampPluginSDK.vcproj cannam@239: cannam@239: This builds the plugin SDK into a single static library, but does cannam@239: not build the example plugins, the host SDK, or the host. (We cannam@239: recommend using static linkage for the SDK rather than distributing cannam@239: it as a DLL, particularly when building plugins.) cannam@239: cannam@239: - build/VampHostSDK.vcproj cannam@239: cannam@239: This builds the host SDK into a single static library, but does not cannam@239: build the plugin SDK, example plugins, or host. cannam@239: cannam@239: - build/VampExamplePlugins.vcproj cannam@239: cannam@239: This builds the example plugins DLL, but does not build the plugin cannam@239: or host SDKs or the host. You don't need to build the plugin SDK cannam@239: before this, because this project simply includes the plugin SDK cannam@239: files rather than using the library. cannam@239: cannam@239: Of course, when using Visual Studio or another IDE to build a plugin cannam@239: or host using the SDK, you may simply add the .h and .cpp files in the cannam@239: vamp-sdk or vamp-hostsdk directories to your existing project. This cannam@239: is the approach taken in the VampExamplePlugins project. cannam@239: cannam@239: As the command-line host has additional library dependencies (namely cannam@239: libsndfile), no pre-packaged project is included to build it. cannam@239: cannam@239: cannam@239: Installing the Example Plugins cannam@239: ------------------------------ cannam@239: cannam@239: To install the example plugins so you can load them in Vamp hosts, cannam@239: copy the files cannam@239: cannam@239: build\release\vamp-example-plugins.dll cannam@239: and cannam@239: examples\vamp-example-plugins.cat cannam@239: cannam@239: to cannam@239: cannam@239: C:\Program Files\Vamp Plugins cannam@239: cannam@239: cannam@239: Plugin Linkage cannam@239: -------------- cannam@239: cannam@239: Vamp plugins are distributed as dynamic libraries (DLLs). A properly cannam@239: packaged Vamp plugin DLL should export exactly one public symbol, cannam@239: namely the Vamp API entry point vampGetPluginDescriptor. cannam@239: cannam@239: One nice tidy way to achieve this with Visual Studio is to add the cannam@239: linker option /EXPORT:vampGetPluginDescriptor to your project. (All cannam@239: of the other symbols will be properly hidden, because that is the cannam@239: default for the Visual Studio linker.) The included example plugins cannam@239: project in build/VampExamplePlugins.vcproj does this. cannam@239: cannam@239: Alternatively, you may modify vamp/vamp.h to add the cannam@239: __declspec(dllexport) attribute to the vampGetPluginDescriptor cannam@239: declaration. This is not present by default, because it isn't cannam@239: portable and, as we only want one symbol exported, the above linker cannam@239: option works equally well without code changes. cannam@239: cannam@239: (If you don't take at least one of these actions, your plugin library cannam@239: simply will not load in any host.) cannam@239: cannam@239: cannam@239: Using MinGW/Cygwin cannam@239: ------------------ cannam@239: cannam@239: Refer to README.linux for build instructions using the GNU toolchain. cannam@239: