So, again with this old theme.
Since _ITERATOR_DEBUG_LEVEL became a thing, release libs don't link with debug builds and vice-versa. This makes addon development for post Orbiter 2016 versions a bit harder than before as an Orbiter installation will only support the compilation of the addon in either debug or release, and to compile in the other mode, Orbiter needs to be recompiled.
The options I see are:
a) start playing with _ITERATOR_DEBUG_LEVEL, and that might allow debug/release mixing again;
b) change the Orbiter build process so that both release and debug libs (e.g., Orbitersdk.lib and Orbitersdkd.lib) are generated, devs then link their builds to the correct libs;
c) change nothing, and let the devs handle Orbiter debug builds themselves.
Option b is the one that makes most sense to me.
Since _ITERATOR_DEBUG_LEVEL became a thing, release libs don't link with debug builds and vice-versa. This makes addon development for post Orbiter 2016 versions a bit harder than before as an Orbiter installation will only support the compilation of the addon in either debug or release, and to compile in the other mode, Orbiter needs to be recompiled.
The options I see are:
a) start playing with _ITERATOR_DEBUG_LEVEL, and that might allow debug/release mixing again;
b) change the Orbiter build process so that both release and debug libs (e.g., Orbitersdk.lib and Orbitersdkd.lib) are generated, devs then link their builds to the correct libs;
c) change nothing, and let the devs handle Orbiter debug builds themselves.
Option b is the one that makes most sense to me.