[cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread James Bigler
In 2.8.12 and 2.8.11.2 I noticed the following problem for VS 2012 builds. VS 2010 builds are fine. Also CMake 2.8.10.1 works just fine. VS 2012 doesn't link the objects into a library. It fails to run the link command at all. I'm trying to figure out why. I'm comparing the differences betwee

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread Brad King
On 09/12/2013 03:08 PM, James Bigler wrote: > In 2.8.12 and 2.8.11.2 I noticed the following problem for VS 2012 builds. > VS 2010 builds are fine. Also CMake 2.8.10.1 works just fine. > > VS 2012 doesn't link the objects into a library. [snip] > Broken project: > Condition="'$(Configuration)|$(

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread James Bigler
On Thu, Sep 12, 2013 at 1:32 PM, Brad King wrote: > On 09/12/2013 03:08 PM, James Bigler wrote: > > In 2.8.12 and 2.8.11.2 I noticed the following problem for VS 2012 > builds. > > VS 2010 builds are fine. Also CMake 2.8.10.1 works just fine. > > > > VS 2012 doesn't link the objects into a libra

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread James Bigler
On Thu, Sep 12, 2013 at 3:07 PM, Brad King wrote: > On 09/12/2013 04:57 PM, James Bigler wrote: > > This seems kind of confusing when the default for all the other VS > > generators is to link in the output of the custom command. Does > > that not seem like a problem? > > The goal is to link all

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread James Bigler
On Thu, Sep 12, 2013 at 3:28 PM, James Bigler wrote: > On Thu, Sep 12, 2013 at 3:07 PM, Brad King wrote: > >> On 09/12/2013 04:57 PM, James Bigler wrote: >> > This seems kind of confusing when the default for all the other VS >> > generators is to link in the output of the custom command. Does

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread Brad King
On 09/12/2013 04:57 PM, James Bigler wrote: > This seems kind of confusing when the default for all the other VS > generators is to link in the output of the custom command. Does > that not seem like a problem? The goal is to link all .obj files listed in the target exactly once. According to Tes

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread James Bigler
On Thu, Sep 12, 2013 at 2:49 PM, Brad King wrote: > On 09/12/2013 04:45 PM, James Bigler wrote: > > I don't actually add the object file to the build, because VS would > > link in the output of the custom command > > That's the exact problem the change I linked fixes. > You should add the object

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-12 Thread Brad King
On 09/12/2013 04:45 PM, James Bigler wrote: > I don't actually add the object file to the build, because VS would > link in the output of the custom command That's the exact problem the change I linked fixes. You should add the object if you want it linked. -Brad -- Powered by www.kitware.com V

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-13 Thread Brad King
On 09/12/2013 05:36 PM, James Bigler wrote: > I discovered a long time ago that VS would link the output of a custom > command. I just ran local experiments with VS 6, 7.1, 8, and 9 by manually modifying the ExternalOBJ test project in the IDE and building. Results: - MAIN_DEPENDENCY has no eff

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-13 Thread Brad King
On 09/13/2013 02:09 PM, James Bigler wrote: > Yeah, this is fine. I tried it on VS 9, 10, and 11. Great, thanks for testing. Applied: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ef27fa67 -Brad -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitwa

Re: [cmake-developers] Linking projects with no C or CPP files

2013-09-13 Thread James Bigler
On Fri, Sep 13, 2013 at 8:21 AM, Brad King wrote: > On 09/12/2013 05:36 PM, James Bigler wrote: > > I discovered a long time ago that VS would link the output of a custom > command. > > I just ran local experiments with VS 6, 7.1, 8, and 9 by manually modifying > the ExternalOBJ test project in t