Martin Buchholz <martin(a)xemacs.org> writes:
> CDE is not X11. It is a software package that requires and extends X.
Then why does /usr/dt include base X11 libraries on some systems?
sb> If I tell configure that I don't want any stinking CDE/Motif by
sb> an unfortunately large number of options, then what business does it
sb> have sticking that directory ahead of others that I have explicitly
sb> asked to be put ahead via --x-includes and --x-libraries. Excuse me,
sb> but configure is clearly broken in this area.
> You CAN specify the location of the BASE X11 using --x-includes and
> --x-libraries. That has nothing to do with whether CDE is used. CDE
> is not X11. CDE === KDE === GNOME !== X11.
Cool.
> Since the CDE libraries use symbols in the X11 libraries, they have to
> come prior to X11 in the link line.
This is all fine.
> It is an autoconf limitation that there can only be one x-includes
> directory and only one x-libraries directory, which does not reflect
> the real world. That is an autoconf design bug, which we could work
> around. Unfortunately, it is fuzzy exactly what X11 is.
O.K.
>>> Does anyone actually have a real live PROBLEM that removing /usr/dt
>>> would solve? There would certainly be many problems that it would
>>> introduce.
sb> Yes. I couldn't build an XEmacs binary on HP/UX against /usr/contrib
sb> X11R6 libraries without manually modifying configure to make /usr/dt
sb> go away.
> I don't believe you.
Whatever.
> --site-libraries, --site-runtime-libraries and --site-includes
> allows you to specify directories that ALWAYS get priority (modulo
> bugs, of course).
I didn't have the builder attempt that. After --x-includes and
--x-libraries didn't work, he gave up trying to work within the system
and used brute force.
sb> I have that patch sitting in my incoming queue. I'm almost in enough
sb> of a foul mood over this to consider applying it.
> A patch that would do what, exactly? Does our HP-UX beta community
> want it?
I have no idea.
> Can you give me an HP-UX account?
No. I don't have one myself -- and I suppose that also is part of the
frustration.
The question stands:
There is already a flag based on whether Motif is needed. Why can't
the configure dependency on /usr/dt be based on whether either Motif
or CDE are either autodetected or requested?
Or else, why the hell does configure peek into /usr/contrib/... and
fuck itself up with /usr/dt when sufficient configure options are
given to make it clear that CDE/Motif are *not* wanted?
Inquiring minds want to know.