> I agree. The problem is when I *don't* say I want to build the viewer,
> and it errors out the whole configuration process, instead of simply
> determining that I don't have the necessary tools, and taking the viewer
> out of the list of things to be built.
Ideally, sensible defaults (i.e. lowest-common denominator, with
error-checking.) If you require libpng/png.h, for example, and it's not
found, fall back to libppm/ppm.h, and if not found, throw a (human-worded)
error message about the missing component(s) and perhaps where to get them
or how to fix it.
If the user wants 'advanced' options enabled, such as palmosbuild or
--build=viewer --build=desktop, etc. and they don't have the tools, the same
or similar checking should occur. Fatal errors without graceful checking are
just ugly, and can lead to more bug reports than we probably care to see.
> If one configures with "./configure --enable-palmosbuild", then perhaps an
> error conclusion is appropriate.
Can we try to flatten this a bit, and use something like:
--with-viewer --with-desktop --with-unpluck, etc? Using long arcane
(easy to misspell) options probably aren't the best choice for usability.
Just a thought.
d.
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
