Use our own export macro

This commit is contained in:
Robbert van der Helm
2022-04-15 14:00:35 +02:00
parent 6e2fff5710
commit c2de0cce2e
5 changed files with 10 additions and 10 deletions
+3 -5
View File
@@ -24,8 +24,6 @@
using namespace std::literals::string_literals;
#define VST_EXPORT __attribute__((visibility("default")))
// The main entry point for VST2 plugins should be called `VSTPluginMain``. The
// other one exist for legacy reasons since some old hosts might still use them
// (EnergyXT being the only known host on Linux that uses the `main` entry
@@ -40,7 +38,7 @@ using namespace std::literals::string_literals;
* manual memory management. Clean up is done when we receive the `effClose`
* opcode from the VST2 host (i.e. opcode 1).`
*/
extern "C" VST_EXPORT AEffect* VSTPluginMain(
extern "C" YABRIDGE_EXPORT AEffect* VSTPluginMain(
audioMasterCallback host_callback) {
try {
// This is the only place where we have to use manual memory management.
@@ -73,8 +71,8 @@ extern "C" VST_EXPORT AEffect* VSTPluginMain(
// XXX: GCC doens't seem to have a clean way to let you define an arbitrary
// function called 'main'. Even JUCE does it this way, so it should be
// safe.
extern "C" VST_EXPORT AEffect* deprecated_main(
extern "C" YABRIDGE_EXPORT AEffect* deprecated_main(
audioMasterCallback audioMaster) asm("main");
VST_EXPORT AEffect* deprecated_main(audioMasterCallback audioMaster) {
YABRIDGE_EXPORT AEffect* deprecated_main(audioMasterCallback audioMaster) {
return VSTPluginMain(audioMaster);
}
+1 -1
View File
@@ -86,7 +86,7 @@ bool DeinitModule() {
* the plugin in our Wine application, retrieve its information and supported
* classes, and then recreate it here.
*/
SMTG_EXPORT_SYMBOL Steinberg::IPluginFactory* PLUGIN_API GetPluginFactory() {
YABRIDGE_EXPORT Steinberg::IPluginFactory* PLUGIN_API GetPluginFactory() {
// The host should have called `InitModule()` first
assert(bridge);