Re: [Plplot-devel] Third checkpoint for the PLplot Cmake build system

[Maurice L. <mj...@br...>]

How does the new system deal with configuration of optional features /
drivers?  I have come to rely a lot on being able to precisely tailor the
build using a site file i.e.

$ CONFIG_SITE=~/config/cf_plplot.in ./configure

where e.g. for a stripped-down build cf_plplot.in might have stuff in it like:

# this function used to set configuration vars so that command-line overrides
# are not broken by it!
my_default() { eval "if test -z \"\$$1\"; then $1=$2 ; fi" ; }

# These are used to set --with* defaults.  In plplot these are used for major
# configuration options, i.e. those with the greatest impact on the build.

my_default with_opt             yes
my_default with_debug           yes
my_default with_double          yes

# Optional libraries
my_default with_qhull           no
my_default with_csa             no
my_default with_freetype        no
my_default with_pthreads        no

# These are used to set --enable* defaults.  In plplot these are used for
# optional features -- typically language bindings and drivers.

# Language bindings.
my_default enable_f77           no
my_default enable_cxx           no
my_default enable_octave        no
my_default enable_tkwin         no
my_default enable_java          no
my_default enable_python        no

# Dynamic drivers
my_default enable_dyndrivers    yes

# Drivers we want for sure
my_default enable_png           yes
my_default enable_jpeg          yes

# Drivers we don't want, mostly legacy stuff
...

-- 
Maurice LeBrun