On Sun, Sep 11, 2005 at 01:59:32PM -0400, Thomas Dickey wrote:
> On Sun, Sep 11, 2005 at 07:38:48PM +0200, Kurt Roeckx wrote:
> > Can you elaborate on that? Break in what way? It could find the
> > wrong include path?
>
> As I read the comment, it sounds as if you're thinking that the macro
> that doesn't check for Xt can replace the one that does.
I'm sorry, but I really can't follow you ... Is there a need to
check that Xt is exists for all packages?
I can understand that some packages do need Xt, but that's not
what the intention of those macro's is. From the manual:
- Macro: AC_PATH_X
Try to locate the X Window System include files and libraries. If
the user gave the command line options `--x-includes=DIR' and
`--x-libraries=DIR', use those directories. If either or both
were not given, get the missing values by running `xmkmf' on a
trivial `Imakefile' and examining the `Makefile' that it produces.
If that fails (such as if `xmkmf' is not present), look for the
files in several directories where they often reside. If either
method is successful, set the shell variables `x_includes' and
`x_libraries' to their locations, unless they are in directories
the compiler searches by default.
If both methods fail, or the user gave the command line option
`--without-x', set the shell variable `no_x' to `yes'; otherwise
set it to the empty string.
- Macro: AC_PATH_XTRA
An enhanced version of `AC_PATH_X'. It adds the C compiler flags
that X needs to output variable `X_CFLAGS', and the X linker flags
to `X_LIBS'. Define `X_DISPLAY_MISSING' if X is not available.
This macro also checks for special libraries that some systems
need in order to compile X programs. It adds any that the system
needs to output variable `X_EXTRA_LIBS'. And it checks for
special X11R6 libraries that need to be linked with before
`-lX11', and adds any found to the output variable `X_PRE_LIBS'.
Are you saying that Xt is a "special libraries that some
systems need in order to compile X programs" ? I don't
think that is what the intention is.
To create the macro, they just had to pick an include file
and try to do something with it to see if it exists, and
they should have picked a more general one like X.h or
Xlib.h.
If the package in question needs to check that Xt is
available, it should use a macro for that, and not a
general one that searches for the include and library
paths.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
