Why are we hardcoding glib-config and gnome-config?

[Robert Graham Merkel]

Rob, below is a snippet of gnucash's configure.in.  I'm trying to 
figure out why GLIB_CONFIG_BIN and GNOME_CONFIG_BIN are explicitly 
set in line 180 and line 203 respectively.  Is this a bug?  It works
fine for me with those two lines commented out.

------------

    180 # Let the user specify glib paths:
    181 GLIB_CONFIG_BIN="glib-config"
    182 AC_ARG_WITH( glib-config,
    183   [  --with-glib-config=executable  which glib-config to use to find glib ],
    184   GLIB_CONFIG_BIN="$with_glib_config")
    185 
    186 # If the user hasn't specified the binary, then try to find it.
    187 if test x"${GLIB_CONFIG_BIN}" = x
    188 then
    189   AC_PATH_PROG(GLIB_CONFIG_BIN, glib-config, GLIB_CONFIG_NOT_FOUND)
    190 fi
    191
    192 if test "${GLIB_CONFIG_BIN}"x != GLIB_CONFIG_NOT_FOUNDx
    193 then
    194   GLIB_CFLAGS=`${GLIB_CONFIG_BIN} --cflags`
    195   GLIB_LIBS=`${GLIB_CONFIG_BIN} --libs`
    196 fi
    197
    198 AC_SUBST(GLIB_CONFIG_BIN)
    199 AC_SUBST(GLIB_CFLAGS)
    200 AC_SUBST(GLIB_LIBS)
    201
    202 # Let the user specify gnome paths:
    203 GNOME_CONFIG_BIN="gnome-config"
    204 AC_ARG_WITH( gnome-config,
    205   [  --with-gnome-config=executable  which gnome-config to use to find gnome ],
    206   GNOME_CONFIG_BIN="$with_gnome_config")
    207
    208 # If the user hasn't specified the binary, then try to find it.
    209 if test x"${GNOME_CONFIG_BIN}" = x
    210 then
    211   AC_PATH_PROG(GNOME_CONFIG_BIN, gnome-config, GNOME_CONFIG_NOT_FOUND)
    212 fi
    213 AC_SUBST(GNOME_CONFIG_BIN)



------------------------------------------------------------
Robert Merkel	                           rgmerk@mira.net

------------------------------------------------------------