On Mon, Jun 13, 2011 at 6:23 PM, Bill Hoffman wrote:
> On 6/13/2011 11:02 AM, Szilárd Páll wrote:
>>
>> I would also very much like to see some form of grouping to be
>> possible in ccmake. Right now, the only way to avoid clutter is to
>> mark the large majority of the variables as advanced and k
On 6/13/2011 11:02 AM, Szilárd Páll wrote:
I would also very much like to see some form of grouping to be
possible in ccmake. Right now, the only way to avoid clutter is to
mark the large majority of the variables as advanced and keep only the
ones that would be used frequently used and this is s
zy/crazy :)
>
> Tim
>
> - Original Message -
> From: "Michael Wild"
> To: cmake@cmake.org
> Sent: Monday, June 13, 2011 6:09:07 AM
> Subject: Re: [CMake] ccmake options organization
>
> On 06/13/2011 11:01 AM, Alexander Neundorf wrote:
>> On Friday 10
o see what others thought and if our guys are
just lazy/crazy :)
Tim
- Original Message -
From: "Michael Wild"
To: cmake@cmake.org
Sent: Monday, June 13, 2011 6:09:07 AM
Subject: Re: [CMake] ccmake options organization
On 06/13/2011 11:01 AM, Alexander Neundorf wrote:
>
On 06/13/2011 11:01 AM, Alexander Neundorf wrote:
> On Friday 10 June 2011, Tim Gallagher wrote:
>> Hi all,
>>
>> We have a code that has a lot of options to enable/disable at compile time,
>> and we'd also like to use ccmake to generate input files to run the code
>> (possibly several hundred opti
On Friday 10 June 2011, Tim Gallagher wrote:
> Hi all,
>
> We have a code that has a lot of options to enable/disable at compile time,
> and we'd also like to use ccmake to generate input files to run the code
> (possibly several hundred options combined). But the way the curses gui
> organizes th
Hi,
I have run into the same trouble and I've started on a local branch to
add a filter option to ccmake as well as others improvement. As you
probably know the cmake GUI already provides such options.
Cheers,
-Nico
On Fri, Jun 10, 2011 at 7:29 PM, Tim Gallagher wrote:
> Hi all,
>
> We have a
Hi all,
We have a code that has a lot of options to enable/disable at compile time, and
we'd also like to use ccmake to generate input files to run the code (possibly
several hundred options combined). But the way the curses gui organizes things
makes it really hard/tedious to keep track of thi