Gonzalo Garramuño wrote:
Alexander Neundorf wrote:
Yes.
In KDE we have the macro MACRO_OPTIONAL_FIND_PACKAGE(), which adds an
option around the find_package() call:
http://websvn.kde.org/trunk/KDE/kdelibs/cmake/modules/MacroOptionalFindPackage.cmake?revision=520790view=markup
Beside that,
Bill Hoffman escreveu:
will be set. The real answer is that the command line is a poor
interface to cmake projects. The new QT GUI is a much better way to go.
Don't say that... I think that a command line interface capability
should be pursued, even if it's non-optimal. God knows if
On Dec 19, 2007 9:09 AM, Bill Hoffman [EMAIL PROTECTED] wrote:
However, this has been discussed many times
over the years, and I still don't think a good solution has been found.
Worse Is Better. From a marketing standpoint, this issue could have
been solved a long time ago. You want people
James Bigler wrote:
What is it that people want beyond -DBUILD_THIS_THAT_WHATEVER:BOOL=TRUE
could provide?
Do they want: --enable-build_this_that_whatever?
People that work with embedded systems might want a stripped down
version of a library, for instance. So disabling features might be
On Tuesday 18 December 2007, Rodolfo Schulz de Lima wrote:
James Bigler wrote:
What is it that people want beyond -DBUILD_THIS_THAT_WHATEVER:BOOL=TRUE
could provide?
Do they want: --enable-build_this_that_whatever?
People that work with embedded systems might want a stripped down
Alexander Neundorf wrote:
I have (currently) two ideas:
either a special file, e.g. CMakeCustomArgs.txt, which in some way sets up the
custom command line parameters.
There's a beauty in having everything inside CMakeLists.txt
Or have a cmake modules, which handles this stuff, and which
On Dec 18, 2007 12:01 PM, Rodolfo Schulz de Lima [EMAIL PROTECTED] wrote:
I think that the scope of where argument definitions should be defined
should be well defined. The example I gave of each cmake --help
evocation returning a different set of arguments shouldn't be allowed.
I disagree.
Rodolfo Schulz de Lima wrote:
Alexander Neundorf wrote:
I have (currently) two ideas:
either a special file, e.g. CMakeCustomArgs.txt, which in some way
sets up the custom command line parameters.
There's a beauty in having everything inside CMakeLists.txt
Not only that, but this becomes
Bill Hoffman wrote:
Brandon Van Every wrote:
Exactly. Anything could happen is a lot of fretting about nothing.
I am thinking a separate file would be the best approach for this.
Something like CMakeOptions.cmake, it gets read in and adds command line
options to cmake. It can include
Alexander Neundorf wrote:
Yes.
In KDE we have the macro MACRO_OPTIONAL_FIND_PACKAGE(), which adds an option
around the find_package() call:
http://websvn.kde.org/trunk/KDE/kdelibs/cmake/modules/MacroOptionalFindPackage.cmake?revision=520790view=markup
Beside that, it is really just a matter
10 matches
Mail list logo
