[Xastir] cygwin compile problem

[Tom Russo]

On Mon, Dec 18, 2006 at 07:30:41AM -0800, we recorded a bogon-computron collision of the <archer at eskimo.com> flavor, containing:
> On Mon, 18 Dec 2006, Curt, WE7U wrote:
> 
> > So I see your point Tom...  Is there a way we can use
> > AC_CHECK_HEADERS() and AC_CHECK_LIB() against non-standard
> > locations?  My Autoconf/automake/libtool book doesn't go into much
> > detail on things like this.  Maybe the only way to know for sure is
> > to go look at the code for the m4 macros themselves?
> >
> > If we could set up some paths before we called the m4 macros it
> > might simplify a lot of our configure code.
> 
> I see some examples here:
> 
> <http://www.mail-archive.com/gnash-commit%40gnu.org/msg00509.html>
> 
> Grep for "/sw/lib" or "/opt/lib".

Ick.

That looks like a brute force attempt to search every possible combination
of non-standard locations.  Furthermore, they're searching in a completely
non-standard way for the existence of certain header files, which is not
how AC_CHECK_HEADER and AC_CHECK_LIB work --- the latter actually check if
the compiler can find and use the headers, not just that they exist.

Using system-specific CPPFLAGS and LDFLAGS is a much better way to do this
than the kinds of hacks present in the gnash-commit you posted up there.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick