Mercurial > hg > vamp-plugin-sdk
comparison README @ 212:d643927816aa
* Update README to describe example plugins VC project file and
include a note about exporting the entry point symbol
author | cannam |
---|---|
date | Tue, 21 Oct 2008 09:57:12 +0000 |
parents | 8c8854a78dcd |
children | 930b51de9c28 |
comparison
equal
deleted
inserted
replaced
211:caa9d07bb9bd | 212:d643927816aa |
---|---|
182 This SDK is intended for use on Windows, OS/X, Linux, and other POSIX | 182 This SDK is intended for use on Windows, OS/X, Linux, and other POSIX |
183 platforms. | 183 platforms. |
184 | 184 |
185 * Windows | 185 * Windows |
186 | 186 |
187 A project file for Visual Studio is included (VampPluginSDK.vcproj). | 187 Two Visual C++ project files are included: |
188 This builds the SDK library, but does not build the example plugins or | 188 |
189 command-line host. | 189 VampPluginSDK.vcproj -- builds the SDK into a single static |
190 library, but does not build the example plugins or host | |
191 | |
192 VampExamplePlugins.vcproj -- builds the example plugins DLL, but | |
193 does not build the library or command-line host | |
190 | 194 |
191 Alternatively, when using Visual Studio or another IDE to build a | 195 Alternatively, when using Visual Studio or another IDE to build a |
192 plugin or host using the SDK, you can simply add the .cpp files in the | 196 plugin or host using the SDK, you may prefer to simply add the .h and |
193 vamp-sdk and vamp-sdk/hostext directories to your existing project. | 197 .cpp files in the vamp-sdk and vamp-sdk/hostext directories to your |
198 existing project. | |
199 | |
200 As the command-line host has additional library dependencies (namely | |
201 libsndfile), no pre-packaged project is included to build it. | |
202 | |
203 When using Visual C++ to build plugins, you will need to ensure that | |
204 the plugin entry point (vampGetPluginDescriptor) is exported from the | |
205 DLL so that the plugins can be loaded. One way to achieve this is to | |
206 add the linker option /EXPORT:vampGetPluginDescriptor to your project. | |
207 The included VampExamplePlugins.vcproj does this. | |
194 | 208 |
195 If you are using a Cygwin or MinGW GNU toolchain, use the included | 209 If you are using a Cygwin or MinGW GNU toolchain, use the included |
196 Makefile (see Linux and other POSIX platforms below). | 210 Makefile (see Linux and other POSIX platforms below). |
197 | 211 |
198 * OS/X | 212 * OS/X |
202 | 216 |
203 Note that the host requires that you have libsndfile | 217 Note that the host requires that you have libsndfile |
204 (http://www.mega-nerd.com/libsndfile/) installed. To build only the | 218 (http://www.mega-nerd.com/libsndfile/) installed. To build only the |
205 SDK and examples, "make -f Makefile.osx sdk examples". | 219 SDK and examples, "make -f Makefile.osx sdk examples". |
206 | 220 |
207 If you are using an IDE, you may prefer to simply add the .cpp files | 221 If you are using an IDE, you may prefer to simply add the .h and .cpp |
208 in the vamp-sdk and vamp-sdk/hostext directories to your existing | 222 files in the vamp-sdk and vamp-sdk/hostext directories to your |
209 project. | 223 existing project. |
210 | 224 |
211 * Linux and other POSIX platforms | 225 * Linux and other POSIX platforms |
212 | 226 |
213 To build the SDK, example plugins, and command-line host, edit the | 227 To build the SDK, example plugins, and command-line host, edit the |
214 Makefile to suit your platform according to the comments in it, then | 228 Makefile to suit your platform according to the comments in it, then |