ExternalProject's CONFIGURE_COMMAND - can I "extend" instead of replacing it?

[ben.boeckel (Ben Boeckel (Kitware))]

@MaxEd

The recommended way to do this is to modify CONFIGURE_COMMAND and add ${CMAKE_COMMAND} -E env VAR=VALUE to it

That’s probably the easiest, yes. Our superbuild has a patchset layer on top of ExternalProject to handle a PROCESS_ENVIRONMENT that handles such things on top of the configure, build, and install commands. It’s something I’ve wanted to clean up and actually get in ExternalProject proper, but I’ve not had the time . It also needs some adaptation to support things like:

• CONFIGURE_ENV
• BUILD_ENV
• etc.