Review: make flags: USE_FIELD3D, USE_JASPER

Make it easy to avoid compiling with field3d or Jasper, even if they are found on your build system (e.g., if you don't need them and can't rely on their being present on your deployment machines).

[Chris Foster, 2011-01-08 04:23:27]

LGTM, with some minor comments -

http://codereview.appspot.com/3826043/diff/1/src/field3d.imageio/CMakeLists.txt
File src/field3d.imageio/CMakeLists.txt (right):

http://codereview.appspot.com/3826043/diff/1/src/field3d.imageio/CMakeLists.t...
src/field3d.imageio/CMakeLists.txt:7: message (STATUS "Field3D not found:
field3d plugin will not be built")
It's a small thing, but this status message isn't technically correct if the
user has set USE_FIELD3D=FALSE, it could potentially be confusing.

http://codereview.appspot.com/3826043/diff/1/src/libOpenImageIO/CMakeLists.txt
File src/libOpenImageIO/CMakeLists.txt (left):

http://codereview.appspot.com/3826043/diff/1/src/libOpenImageIO/CMakeLists.tx...
src/libOpenImageIO/CMakeLists.txt:132: message (STATUS "Jasper not found:
jpeg2000 plugin will not be built")
This status message is redundant now given the new one in
jasper.imageio/CmakeLists.txt.  Same for the Field3D message below.