Yes, that's what I was driving at. In the current CVS version of configure.in, various things that are enabled by default (the PalmOS viewer, the desktop, the manual) do not check to see if the environment permits them to be built. I think the simplest thing to do is to disable them by default, and the right thing to do is to add the proper checking. I'm going to add the proper checking for the desktop and the manual; I see that Michael has been working on the viewer configuration, so I don't want to fiddle with that till he's done. I thought I'd just change the default to disable, so that one would have to configure with --enable-palmosbuild to enable it.
> 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. Bill _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
