I want to use Rhino Tools in an application (for the Binsor support). There isn't a binary release so I'm downloading the source and compiling it. It compiles the debug binaries no problem, but the release build fails.
The app that I'm developing will be deployed with release binaries, but will have to reference the debug build of Rhino Tools.
What are the ramifications of deploying release code along with some dependencies that are debug binaries? Is it going to kill performance?
One possible ramification if you're using the Microsoft C/C++ toolset is that the Debug build will be dependent on the debug runtime DLL (msvcrXXd.dll).
According to MSVC's license, that DLL is not distributable.
Performance won't be a big problem, but you're usually not allowed to distribute the c-runtime debug binaries (statically linked or the dll). At least if you're using VisualStudio, Microsoft doesn't allow to ship the debug binaries required, only the release ones.
But if the release build fails, why don't you try to fix that build? Or at least report your problems to the Rhino guys?
I figured out the build issue I was having with Rhino-Tools. I've also come to the conclusion that debug binaries in production environments is simply wrong and that is was a bit dumb of me to think about do it. :-)