On Mon, Nov 21, 2011 at 1:41 PM, Brad King <brad.k...@kitware.com> wrote:
> On 11/21/2011 3:33 PM, James Bigler wrote: > >> On Mon, Nov 21, 2011 at 9:39 AM, Brad King <brad.k...@kitware.com<mailto: >> brad.k...@kitware.com>**> wrote: >> On 11/18/2011 12:50 PM, James Bigler wrote: >> What I'm envisioning is developing a new custom build tool, >> call it CMake Custom Command (or CCC for short) >> >> Would the custom commands in the project files just invoke this tool >> on every build? >> >> Yes, any custom command in the project would invoke the same rule file. >> > > Think of it as replacing VS's "interesting" custom build command rule > with our own. > > I've thought about this idea a few times before in the context of custom > commands with build-time implicit dependency scanning. It's essentially > a "make" tool, isn't it? Since "nmake" always comes with VS, perhaps it > can be utilized for this. > > -Brad > Yeah, I haven't thought of it as a 'make' tool, but you are correct. It would do something to analyze dependencies, report back to VS what they are, then run some custom command if VS says that the dependencies are out of date. This is how I believe the MSbuild rules are designed to function.
-- 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
