[cmake-developers] VS 2010/MSbuild's custom build tool issues and a proposal

James Bigler jamesbigler at gmail.com
Mon Nov 21 15:55:11 EST 2011


On Mon, Nov 21, 2011 at 1:47 PM, Bill Hoffman <bill.hoffman at kitware.com>wrote:

>
> On Nov 21, 2011 3:41 PM, "Brad King" <brad.king at 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.king at kitware.com<mailto:
> brad.king at 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.
> >
> >
>
> That is kind of what we do with xcode and make.  Does nmake install with
> express versions?
>
This page seems to suggest so, but I'm having trouble determining this for
certain, and I don't want to install it for fear of it messing up my
existing VS installations.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20111121/95459c17/attachment.html>


More information about the cmake-developers mailing list