OpenCMISSLocalConfig doesn't differentiate between Debug and Release build types

[chrispbradley]

The OpenCMISSLocalConfig.cmake file is stored in an archpath under manage. However, it is stored outside the final build type directory in the archpath. This means that different build types can not have different configs. I need different configs for, say, Debug and Release build types in order to turn on/off various debug, profiling and testing features. Options to fix this are

1. Move OpenCMISSLocalConfig.cmake into the build type directory (preferred as it will keep everything together) or
2. Have an additional local config file in the build type directory that is read as well (not preferred as it may harder for somebody to configure as they have to do things in two different places).
   In addition to the above the first release directory under manage is redundant.

[hsorby]

The OpenCMISSLocalConfig doesn't differentiate between Debug and Release because they are not fully fledged configuration parameters like MPI is for example. Depending on how you define the profiling and testing features they may also not be fully fledged configuration options. The OpenCMISSLocalConfig is only for fully fledged configuration options and therefore shouldn't be moved into a build type sub-directory.

[hsorby]

The first release directory under manage may well be redundant but it is consistent.

[chrispbradley]

Debug and Release etc. might not be fully fledged configuration parameters for you but they are for me. The options change what code compiles, what libraries are linked and are completely consistent with the other options in the OpenCMISSLocalConfig.cmake file. If the fully fledged configuration options are required to be differentiated with the build type then there is no reason why the config file cannot sit under the build type directory in the archpath. I'm glad you agree that the first release under manage is redundant.