Autres/audacity
1
0
Fork 0
mirror of https://github.com/cookiengineer/audacity synced 2025-10-15 15:11:12 +02:00
Code Issues Releases Wiki Activity

Update libvamp to 2.5.

Browse Source
This commit is contained in:
lllucius
2013-10-31 06:33:59 +00:00
parent c8aa505879
commit 6fef6dd8b4
77 changed files with 6254 additions and 3598 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
lib-src/libvamp/build/README.osx
View File

@@ -2,25 +2,40 @@
The Vamp Plugin SDK -- Platform Notes for OS/X
==============================================
Prerequisites
-------------
You must have Xcode installed, with the command-line build tools.
(If you are using Xcode 4, you may have to go to Preferences ->
Downloads -> Components and install the Command Line Tools component.)
You must have libsndfile (http://www.mega-nerd.com/libsndfile/)
installed in order to build the command-line host successfully. But
you do not need libsndfile if you only want to build plugins.
Building at the command line
----------------------------
To build the SDK, example plugins, and command-line host:
$ make -f Makefile.osx
$ make -f build/Makefile.osx
You must have libsndfile (http://www.mega-nerd.com/libsndfile/)
installed in order to build the command-line host successfully. To
build only the SDK and examples:
To build only the SDK and example plugins (for example if you do not
have libsndfile installed):
$ make -f Makefile.osx sdk examples
$ make -f build/Makefile.osx sdk examples
See the comments at the top of Makefile.osx for more information about
the libraries and other targets that are built in this way.
If you are using an IDE, you may prefer to simply add the vamp-sdk and
src/vamp-sdk (for plugins) or vamp-hostsdk and src/vamp-hostsdk (for
hosts) directories to your existing project.
If you are using an IDE such as Xcode, you may prefer to simply add
the vamp-sdk and src/vamp-sdk (for plugins) or vamp-hostsdk and
src/vamp-hostsdk (for hosts) directories to your existing project.
If you are using OS/X 10.6 or older, use Makefile.osx.106 instead of
Makefile.osx.
Installing the Example Plugins
@@ -42,8 +57,14 @@ or
Plugin Linkage
--------------
Vamp plugins are distributed as dynamic libraries (.dylib). A
well-packaged Vamp plugin library should export exactly one public
Vamp plugins are distributed as dynamic libraries (.dylib). An OS/X
dynamic library has a formal installed name, which is recorded in the
library's header: you will need to ensure that this matches the
plugin's filename (e.g. vamp-example-plugins.dylib) by using the
-install_name <name> option at link time. The Makefile.osx provided
with the SDK contains an example of this.
A well-packaged Vamp plugin library should export exactly one public
symbol, namely the Vamp API entry point vampGetPluginDescriptor.
The default for the OS/X linker is to export all of the symbols in the
@@ -68,3 +89,13 @@ build/vamp-plugin.list. There are other methods that will work too,
but this one is simple and has the advantage of requiring no changes
to the code.
Test Your Plugins
-----------------
The Vamp Plugin Tester is a vital utility which you can use to test
your plugins for common problems. It can help you if you're having
problems getting your plugin to work at all, and you're strongly
advised to use it before you release anything. Download it from the
Vamp plugins site now!