Surely, the better approach is to adapt autoconf, such that either the AC_INIT setting of `ac_default_prefix' is more intelligent wrt Win32 (or more specifically, MSYS) paths, or to adapt the AC_OUTPUT reassignment of `prefix=$ac_default_prefix' to incorporate some variant of the MSYS_PREFIX_HACK logic I presented earlier -- my preference would be to have a more intelligent initialisation for `ac_default_prefix', e.g. instead of:
ac_default_prefix=/usr/local
say:
ac_default_prefix=`exec 2>/dev/null;cd /usr/local;pwd -W` ||\ ac_default_prefix=/usr/local
I have tested this alternative initialisation on every system available to me. On SunOS 5.5.1 with `sh', `ksh' and `bash', on
I am sure that this works great if the real Windows path represented by prefix contains embedded spacess. ;-)
Many/most packages will bomb as soon as they encounter spaces in paths.
Bob ====================================== Bob Friesenhahn bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
