Did you know that with only 3 minor preprocessor directives on 2 SDK files you can modify the editorhost sample example so that it becomes a kind of a standalone application that does not require external resources ? And all the while you do not break the SDK.
The need for this might arise if a developer wants to use the versatile VSTGUI controls in his or her applications, far removed from actual audio needs.
The license of the SDK permits us to modify it.
…
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
…
VSTGUI has a standalone library which you can use to build applications using the same WYSIWYG editor for the user interface as the VST3Editor. No need to change any SDK files.
True but the standalone library requires that the resources you use be external to the program and that they need to be available in a particular sub-directory to the running program.
The above method carries the resources within itself just like how the Vst dll does, in a single executable file.
I don’t see this as an advantage. But if you do then OK.
Less baggage, and the PECOFF file already has sections meant to do just that.
Is it permissible to show how ?