Mercurial > hg > vamp-plugin-sdk
comparison README @ 162:8c8854a78dcd
* Update README, .la files etc for 1.3
author | cannam |
---|---|
date | Wed, 09 Jul 2008 09:36:39 +0000 |
parents | 1da43924fa14 |
children | d643927816aa |
comparison
equal
deleted
inserted
replaced
161:7fc1041daa9d | 162:8c8854a78dcd |
---|---|
47 | 47 |
48 | 48 |
49 About this SDK | 49 About this SDK |
50 ============== | 50 ============== |
51 | 51 |
52 This is version 1.2 of the Vamp plugin Software Development Kit. | 52 This is version 1.3 of the Vamp plugin Software Development Kit. |
53 Plugins and hosts built with this SDK are binary compatible with those | 53 Plugins and hosts built with this SDK are binary compatible with those |
54 built using version 1.0 of the SDK. | 54 built using version 1.0 of the SDK. |
55 | 55 |
56 This SDK contains the following: | 56 This SDK contains the following: |
57 | 57 |
74 | 74 |
75 Plugins should subclass Vamp::Plugin and then use Vamp::PluginAdapter | 75 Plugins should subclass Vamp::Plugin and then use Vamp::PluginAdapter |
76 to expose the correct C API for the plugin. Plugin authors should | 76 to expose the correct C API for the plugin. Plugin authors should |
77 read vamp-sdk/PluginBase.h and Plugin.h for code documentation, and | 77 read vamp-sdk/PluginBase.h and Plugin.h for code documentation, and |
78 refer to the example plugin code in the examples directory. Plugins | 78 refer to the example plugin code in the examples directory. Plugins |
79 should link with -lvampsdk. [*NOTE: this has changed from vamp-sdk in | 79 should link with -lvamp-sdk. |
80 previous versions, to avoid conflict with the use of hyphens for | |
81 library versioning schemes on some platforms.] | |
82 | 80 |
83 Hosts may use the Vamp::PluginHostAdapter to convert the loaded | 81 Hosts may use the Vamp::PluginHostAdapter to convert the loaded |
84 plugin's C API back into a Vamp::Plugin object. Host authors should | 82 plugin's C API back into a Vamp::Plugin object. Host authors should |
85 refer to the example host code in the host directory. Hosts should | 83 refer to the example host code in the host directory. Hosts should |
86 link with -lvamphostsdk. [*NOTE: this has changed from vamp-hostsdk | 84 link with -lvamp-hostsdk. |
87 in previous versions, to avoid conflict with the use of hyphens for | |
88 library versioning schemes on some platforms.] | |
89 | 85 |
90 * vamp-sdk/hostext | 86 * vamp-sdk/hostext |
91 | 87 |
92 Additional C++ classes to make a host's life easier (introduced in | 88 Additional C++ classes to make a host's life easier (introduced in |
93 versions 1.1 and 1.2 of the Vamp SDK). | 89 versions 1.1 and 1.2 of the Vamp SDK). |
178 trees, which is why this information is not queried as part of the | 174 trees, which is why this information is not queried as part of the |
179 Vamp plugin's API itself. The Vamp::HostExt::PluginLoader class also | 175 Vamp plugin's API itself. The Vamp::HostExt::PluginLoader class also |
180 provides support for plugin category lookup using this scheme. | 176 provides support for plugin category lookup using this scheme. |
181 | 177 |
182 | 178 |
183 Building and Installing the SDK and Examples | 179 Compiling the SDK and Examples |
184 ============================================ | 180 ============================== |
185 | 181 |
186 To build the SDK, the simple host, and the example plugins, edit the | 182 This SDK is intended for use on Windows, OS/X, Linux, and other POSIX |
183 platforms. | |
184 | |
185 * Windows | |
186 | |
187 A project file for Visual Studio is included (VampPluginSDK.vcproj). | |
188 This builds the SDK library, but does not build the example plugins or | |
189 command-line host. | |
190 | |
191 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 | |
193 vamp-sdk and vamp-sdk/hostext directories to your existing project. | |
194 | |
195 If you are using a Cygwin or MinGW GNU toolchain, use the included | |
196 Makefile (see Linux and other POSIX platforms below). | |
197 | |
198 * OS/X | |
199 | |
200 Run "make -f Makefile.osx" to build the SDK, example plugins, and | |
201 command-line host. | |
202 | |
203 Note that the host requires that you have libsndfile | |
204 (http://www.mega-nerd.com/libsndfile/) installed. To build only the | |
205 SDK and examples, "make -f Makefile.osx sdk examples". | |
206 | |
207 If you are using an IDE, you may prefer to simply add the .cpp files | |
208 in the vamp-sdk and vamp-sdk/hostext directories to your existing | |
209 project. | |
210 | |
211 * Linux and other POSIX platforms | |
212 | |
213 To build the SDK, example plugins, and command-line host, edit the | |
187 Makefile to suit your platform according to the comments in it, then | 214 Makefile to suit your platform according to the comments in it, then |
188 run "make". | 215 run "make". |
189 | 216 |
190 There is a ready-tweaked Makefile for use on OS/X; to use it, run | 217 Note that the host requires that you have libsndfile |
191 "make -f Makefile.osx". | 218 (http://www.mega-nerd.com/libsndfile/) installed. To build only the |
192 | 219 SDK and examples, edit the Makefile then run "make sdk examples". |
193 To use an IDE to build a plugin or host using the Vamp SDK, simply add | 220 |
194 the .cpp files in the vamp-sdk directory to your project. | 221 |
222 Installing the Example Plugins | |
223 ============================== | |
195 | 224 |
196 Installing the example plugins so that they can be found by other Vamp | 225 Installing the example plugins so that they can be found by other Vamp |
197 hosts depends on your platform: | 226 hosts depends on your platform: |
198 | 227 |
199 * Windows: copy the files | 228 * Windows: copy the files |