Hi Michael,
Thank you for the follow-up and sorry for my late response! I
appreciate your suggestions as they basically summarize the problems
I've been having...
On Wed, Dec 8, 2010 at 21:25, Michael Hertling wrote:
> Yes, absolutely, with such relations among executables and libraries,
> the
Didn't know about that, thanks for pointing it. I'll take a look at it.
2010/12/12 Alexander Neundorf
> On Wednesday 08 December 2010, Klaim wrote:
> > Thanks! I'll try this solution.
> >
> > By the way is there a way to list all projects found recursively in a
> > folder?
>
> Didn't follow the
On Sunday 28 November 2010, luxInteg wrote:
> On Sunday 28 November 2010 02:22:56 luxInteg wrote:
> > Greetings,
> >
> > I am learning cmake. I am attempting to compile a small progrmm libxls
> > (available from http://libxls.sourceforge.net/ ) as part of my
> > education.
> >
> > It compiles
On Wednesday 08 December 2010, Klaim wrote:
> Thanks! I'll try this solution.
>
> By the way is there a way to list all projects found recursively in a
> folder?
Didn't follow the thread closely, but did you have a look at the
FeatureSummary.cmake macro ?
It can tell you which packages have been
On Friday 10 December 2010, Bill Hoffman wrote:
> There are a few things we have already started to do that should help
> with the bug tracker issue.
>
> 1. We hare having 4 releases of CMake each year. After each release we
> post to the list and ask people to "vote" for bugs they would like fix
On Friday 10 December 2010, Alan W. Irwin wrote:
> On 2010-12-10 17:01+0100 Pau Garcia i Quiles wrote:
> > On Fri, Dec 10, 2010 at 3:42 PM, Bill Hoffman
wrote:
> >> I have a third idea that we have not yet tried:
> >>
> >> What do people think of automatically closing bugs if they are not
> >> mo
