On Tue, May 28, 2013 at 8:22 AM, Brad King <[email protected]> wrote: > On 05/26/2013 12:04 PM, Robert Dailey wrote: >> I haven't gotten a response yet, I guess you guys stay pretty busy :) > > Huh? I responded here: > > > http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/6800/focus=6933 > >> Am I correct to assume that add_custom_command() still needs a CONFIG >> option to support varying numbers & names of output files per >> configuration, based on my previous description of the problem I'm >> facing? > > Yes, though I think we can use generator expressions as stated in my > other response.
Sorry about that Brad, for some reason I didn't get your last response in my inbox. It's not in spam either. Strange. I like your idea of using an external script to handle this, however, there is certain state I need access to from the last CMake run. Specifically, I have a variable with all of the 'bin' directories where DLLs can be found. To avoid recursive searching in my custom target script to find them each time I build, I suppose I could store them in a cache variable? I was just going to create a CMake script that I run from the custom target. The reason I went with custom commands to begin with is because I originally used cmake's copy_if_different command, but it turned out to be MUCH slower than the out of date checks that the custom command did. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
