Re: Configure 21.1.14 does not find XPM on Cygwin without X11 install ed
Martin Buchholz writes:
>>>>> "David" == David Bush <Bush>
writes:
I would like someone in Windowsland to look at this more deeply.
The fundamental principle of running test programs at configure time
is to use external interfaces in the _same_ way as the real build
process later does. Otherwise you have mismatches between what is
detected and what actually works. I have worked to eliminate such
mismatches over the years.
I would like
#define XPM_NUMBERS
to be removed from the 21.2 configure script. Find another way to fix
this in configure.in.
The configure script does two checks related to the xpm library. The
first one just wants to know what version the header file thinks is
current, what version the library actually contains, and whether the
two match. The second check is to determine whether FOR_MSW is needed
or not. '#define XPM_NUMBERS' allows the configure script to check
the existance and version of the xpm library without having to know
whether FOR_MSW is needed.
A windows build must define FOR_MSW before using the xpm library.
When building with VC++ it is a non-issue because that build mechanism
doesn't use 'configure'. However, the cygwin and mingw (-mno-cygwin)
build mechanisms do and at least the mingw mechanism needs that define
in order to properly detect the xpm library.
This appears to be the way that the original author of the xpm library
intended it to be used.
Craig