On Tuesday 01 November 2011, craig.sc...@csiro.au wrote:
...
> If you do that, you create a circular dependency, since CMake requires Qt
> to build its GUI application. Yes, you could build CMake's command line
> tools only, then Qt, then build CMake's GUI app, or alternatively you
> could install
On Friday, October 28, 2011 13:13:20 Stephen Kelly wrote:
> == Summary ==
>
> I'm considering adding some cmake files to Qt, which would be installed by
> Qt, and which would make it easier for CMake based projects to depend on
> Qt.
>
> I'm CC'ing the cmake developers too see what they think of
On Friday, October 28, 2011 07:58:25 Clinton Stimpson wrote:
> On Friday, October 28, 2011 06:21:23 am Stephen Kelly wrote:
> > On Friday, October 28, 2011 13:56:20 Thiago Macieira wrote:
> > > On Friday, 28 de October de 2011 13:13:20 Stephen Kelly wrote:
> > > > * If you want to be easily found f
On Friday, October 28, 2011 16:24:08 Matt Williams wrote:
> On 28 October 2011 14:44, wrote:
> >
> > I think that's reasonable in general. It's similar to what we do to
> > support pkgconfig. I agree with Thiago's comment that this should be
> > split and we should have one file per shared librar
On Friday, October 28, 2011 13:56:20 Thiago Macieira wrote:
> On Friday, 28 de October de 2011 13:13:20 Stephen Kelly wrote:
> > * If you want to be easily found for others to depend on, you write a
> >
> > Config.cmake file and install it to a location CMake
> > will use>
> > to find t
