So I guess you must be facing some different problem here. Regarding MacOS: There you don’t have to care about that. So that being said, if you have no real need to use the dynamic linked runtime, just stick to the statically linked one and all is fine. You’ll likely find a thread on that round here in a few minutes But to be honest, I always went with static runtime linkage on Windows to avoid the whole topic and I’m currently facing the very same question myself, as I introduced a dependency to a third library that needs the dynamic linked runtime to my recent project. I think both are theoretically possible solutions but it won’t be very convenient to tell the user to execute a second installer in order to make your plugin work. However how can i manage to use the dynamic linking on a computer that doesn’t have the needed libraries? Do i install them with the plugin in the ino setup installer or i tell the user to install them by himself?
