cannam@50: cannam@50: cannam@50:
cannam@50: cannam@21:
cannam@50: VampPluginSDK
cannam@50: 2.1
cannam@50:
cannam@50:
cannam@50: |
cannam@50:
cannam@50:
cannam@50:
cannam@50:
Go to the source code of this file.
cannam@50:cannam@50: Defines | |
#define | _VAMP_IN_PLUGINSDK 1 |
Normal usage should be: | |
#define | _VAMP_SDK_PLUGSPACE_BEGIN(h) |
#define | _VAMP_SDK_PLUGSPACE_END(h) |
#define _VAMP_IN_PLUGINSDK 1 | cannam@21:
Normal usage should be:
cannam@21:Problems will occur when a host includes files directly from the vamp-sdk directory. There are two reasons this might happen: mistake, perhaps owing to ignorance of the fact that this isn't allowed (particularly since it was the normal mechanism in v1 of the SDK); and a wish to incorporate plugin code directly into the host rather than having to load it.
cannam@50:What if the host does include a vamp-sdk header by mistake? We can catch it if it's included before something from vamp-hostsdk. If it's included after something from vamp-hostsdk, it will work OK anyway. The remaining problem case is where nothing from vamp-hostsdk is included in the same file. We can't catch that.
cannam@50: cannam@50:Definition at line 72 of file plugguard.h.
cannam@21: cannam@21:#define _VAMP_SDK_PLUGSPACE_BEGIN | cannam@21:( | cannam@50:cannam@50: | h | ) | cannam@21:cannam@21: |
Definition at line 75 of file plugguard.h.
cannam@21: cannam@21:#define _VAMP_SDK_PLUGSPACE_END | cannam@21:( | cannam@50:cannam@50: | h | ) | cannam@21:cannam@21: |
Definition at line 76 of file plugguard.h.
cannam@21: cannam@21: