Hello, Rhino developers!
We have an important Rhino C++ Windows plugin which has been under development for many years and work on it continues. We have always had an issue with Rhino C++ SDK dependency on MFC, but lately it became critical. The main issues are:
- We are unable to compile our plugin using strict (C++ 17) Conformance mode (
/permissive-) which is required by some other code and dependencies. This forces us to use very outdated dependencies (libraries). If we try to compile our code with/permissive-using the latest Rhino C++ SDK (8.30.26103.11001), we get compilation errors coming from\Rhino 8 SDK\inc\rhinoSdkTMfcPages.hTo reproduce, simply create a basic C++ plugin from a template and set this compilation option. - We are unable to use any other UI and event handling frameworks as they collide with those in MFC (we have dependency on Qt and could use it for event handling and custom dialogs).
With all that said, I recently discovered that you created a C++ SDK for MAC in Rhino WIP which (obviously) does not depend on MFC.
Are there any plans to exclude MFC dependency for the Windows version of C++ SDK? From what I remember, I read that Rhino core does not have MFC dependency, so only C++ SDK left with MFC…
Are there any suggestions on how to resolve compilation issues when using /permisive- option?
Thank you!
Andrey