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
+2 -2
View File
@@ -41,9 +41,9 @@ static const std::string host_name = "yabridge group host version " +
* plugin host and this group plugin host will function identically on both the
* plugin and the Wine VST host side.
*/
int __attribute__((visibility("default")))
int YABRIDGE_EXPORT
#ifdef WINE_USE_CDECL
__cdecl
__cdecl
#endif
main(int argc, char* argv[]) {
// Instead of directly hosting a plugin, this process will receive a UNIX
+2 -2
View File
@@ -39,9 +39,9 @@ static const std::string host_name = "yabridge host version " +
* plugin plugin, and then connect back to the `libyabridge-{vst2,vst3}.so`
* instance that spawned this over the socket.
*/
int __attribute__((visibility("default")))
int YABRIDGE_EXPORT
#ifdef WINE_USE_CDECL
__cdecl
__cdecl
#endif
main(int argc, char* argv[]) {
// We pass the plugin format, the name of the VST2 plugin .dll file or VST3