8 Jan
2012
8 Jan
'12
12:02 a.m.
On Sunday 08 January 2012 00:11:15 Darrell Anderson
wrote:
[...]
Actually I do not understand the problem. If you want to check all
features,
enable they.
It is mainly a novice builder/user usability problem; i.e. if we need to
manually enable all features then there should be a universal, simple way
to get a listing of all features that can be enabled. Opening the
CMakeLists.txt file and reading the entire thing does not count. ;-)
Tim
This
tells the user exactly what is being built. If
the user wants something else, he has a basis to determine
what is missing (or extra) and make the appropriate
changes.
Yes, this sounds palatable. As upstream providers we need to test
everything. Right now doing that is cumbersome.
I understand that individual packagers don't want everything enabled. I
don't either, but I am looking at this as an upstream provider and not
just
a packager. We can't test everything if most of the features are
disabled
by default.