ENH: Provide a way to skip auto-including the BuildSettings.cmake file when importing the whole toolkit from an external project. On Win32, this BuildSettings file would prevent you from building your own project against the toolkit using either a different generator *and*/*or* a compiler that was installed in a non-standard location. This is decision that was made a long time ago to prevent users from shooting themselves in the foot (at the time of Visual Studio 7 taking over Visual Studio 6), but the implementation will make many people's life impossible otherwise. For reference: the BuildSettings.cmake file that is installed holds the flags that were used to build the toolkit, as well as the full paths to a few coresponding compiler tools; if they don't match your own compiler tools by the time you import the toolkit, CMake will give up. There is however no technical reason that you can't use different generators if you are using the exact same compiler version, and obviously the compiler location shoul...