id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
688	Let user choose the I/O tool	Ian Culverwell	Ian Culverwell	"ROPP-10 beta reviewers Christian Marquardt and Leonid Butenko say:
{{{
If binaries are only built using the eccodes library (given that bufrdc hasn't
been maintained since a long time), the standard executables (e.g., eum2bufr) do
not even exist. One way around for a user is to manually create symbolic links
to the existing binaries after installation; this could be automated at
installation time. An alternative option could be to install a user-selectable
version under the default names. In case such behaviour is not implemented, the
READMEs and other documentation should explain the chosen approach and make
users aware that they need to manually add symbolic links or rename some
binaries when building ROPP against ectools.
}}}
I think the general idea of building as many tools as the dependencies allow (e.g. '''ropp2bufr_mobufr''', '''ropp2bufr_ecbufr''' and '''ropp2bufr_eccodes''', if possible), and then pointing ropp2bufr to the code- or user-defined preference is an excellent (and long-overdue) one.  

(The documentation has already been updated to point out the need to link '''ropp2bufr_ecodes''' to '''ropp2bufr''', if they are relying on a file of that name but want to use the ecCodes version of it.)

Consider for ROPP-11.0.
"	task	closed	normal	11.1	ropp_io	10.0	fixed		olewis