Closed AnClark closed 1 year ago
pretty sure this works fine already, Cardinal, ProM and other plugins use this. if you changed this after building just clean and rebuild things again.
Have you ever tested in examples bundled with DPF?
not sure how it would be any different from e.g. https://github.com/DISTRHO/glBars/blob/master/plugins/glBars/Makefile
Tested in a fresh clone of DPF source tree (Rev 03c3616), and compile example "States", problem still occurs.
glBars can build without errors. I wonder where the differences are.
right, I know. glbars defines DISTRHO_PLUGIN_WANT_DIRECT_ACCESS
to 1, while states example does not.
with that flag dpf knows to build some extra bits only once.
I can make this more robust by detecting such build type, but it is still not recommended because we would then have DSP and UI on the same object/DLL file.
My SynthV1 port also set this macro to 1, and problem also occurs there.
it should be a slightly different error then.. or maybe related to it using external-ui. need to check this..
The linker error mainly resides in "multiple definition". Maybe there's something to do with DistrhoMain.cpp or DistrhoPluginLV2.cpp?
EDIT: SynthV1 monolithic issue has been solved by clean-rebuild. (I only use CMake there.)
But issue still exists in example "States", "Info", and possibly other projects.
Hi, falkTX!
By now DPF only supports build separated LV2 plugin. When I try to build a monolithic one (DSP and UI part reside in the same binary), linker error will occur.
For example, I try to build the example
states
, and modify Makefile:Then
make
. At this time, linker error occurs:I see VST2/VST3/CLAP has similar Makefile rules. They can successfully build DSP and UI together. But only LV2 has this issue.