On 10 Dec 1999, Jan Vroonhof <vroonhof(a)math.ethz.ch> wrote:
"Daniel Pittman" <daniel(a)danann.net> writes:
> The option `--with-athena' is available to specify the preferred
> Athena widget set. This takes a range of values such as `flat' or
> `3d' or `next' that specify what libraries to prefer.
Perfect. But please make it clear in the docs that you must set one of
the other options to athena for this to be usefull.
As per usual with development, doco comes last[1] in the development
cycle.
> Without this option being specified, the user gets libXaw.so
> preferred, with the flat or 3d headers according to the 3d-ness of
> libXaw.so. This retains the current behavior of
> `--with-widgets=athena' -- no surprises to people who don't pay
> attention.
Actually I would prefer to have one of the sexier ones be the default
<big>IF</big> we can detect them reliably.
*grin*
Well, I need to actually grab the source and (more importantly) the
headers for the Xaw variants and make sure that I can reliably detect
them. Then I would be happy to implement a thing of `look for sexy
widgets, use them if found'.
At the moment it prefers -lXaw3d to -lXaw, even if -lXaw is a 3D Athena
library. It will refuse to use a non-3d -lXaw if you asked for something
3d.
If you told it to use a 3d library, it can't find the long name version,
and -lXaw is a 3d library, I assume that you know what you are doing and
that you have installed /that/ 3d Xaw over the top of the normal Xaw
library.
> In this vein, `--with-widgets=athena3d' would be the same as
the new
> `--with-athena=3d' and `--with-widgets=athena' for backward
> compatibility.
Is it really needed to be backwards compatible with a few betas?
I don't know. At the moment I have backward compatible configuration in
there, including the blind assumptions that it made about what and where
the Athena libraries were.
This is actually much easier than I had though to achieve. I also have
an instinct that says not breaking peoples assumptions is nice, at least
for a while.
I can drop the backward-compatibility stuff if that's desirable though.
That will break `./configure --with-widgets=athena3d' though.
Um, it's actually working for `configure' now. I don't think that
`lwlib' hacking will take that long.
What's the standard for posting patches to xemacs-patches? You folk
prefer unified diffs, as plain text attachments, yes?
Daniel
Footnotes:
[1] Actually, I wanted to make sure that the configure stuff passed
muster here before writing helpful documentation about it since
that's what I find hardest :)
--
Increasing numbers of private-sector companies are discovering the
efficiency of hiring bright undergraduates or recent graduates and
paying them next to nothing.
-- Washingtonian magazine