Re: Avoiding exponential increase of build configurations?

Hello all,

I have several applications that depend on a project called 'Utils'.
Some of these applications output executable files, others output dll
files. This required me to add DLL configs to the utils project:
DebugDLL and ReleaseDLL.

Now, some applications use MFC and others don't. The ones that don't
use MFC must be able to build on Visual C++ express edition, which
doesn't support MFC. This is tricky because inside Utils there are
some files that use MFC, and they are only used by the MFC apps.

My idea was to add another build config for MFC apps. For example:
DebugMFC, ReleaseMFC, DebugDLLMFC, ReleaseDLLMFC. But this way of
working can't last long since the number of build configurations is
rising exponentially here.

Is there a way that allows for multiple combinations of project
settings that does not result in an exponential growth of build
configs?

Best regards,

Francis