9:46 a.m.
"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.
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.
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?
Jan
10:33 p.m.
New subject: New Athena widget configuration (was Re: Problem with `configure --with-sound')
> 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?
No, only non-beta releases matter. Feel free to experiment with
the betas.
12:06 a.m.
New subject: New Athena widget configuration (was Re: Problem with `configure --with-sound')
>>>> "Jan" == Jan Vroonhof
<vroonhof(a)math.ethz.ch> writes:
Jan> "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.
Jan> Perfect. But please make it clear in the docs that you must set one of
Jan> the other options to athena for this to be usefull.
> 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.
Jan> Actually I would prefer to have one of the sexier ones be the default
Jan> <big>IF</big> we can detect them reliably.
Whatever we decide, we should keep in mind that these libraries are
intended to be installed by copying over the real libraries. So it
would be real nice if xemacs did something reasonable (crashing is not
reasonable):
- if built on a system with athena3d libs, run on a system with athena.
- if built on a system with athena, run on a system with athena3d.
This might be a reason to not build with athena3d support by default,
even on a system that happens to have athena3d libraries - the
generated xemacs binary would be less portable.
Martin
7:58 p.m.
New subject: New Athena widget configuration (was Re: Problem with `configure --with-sound')
Martin Buchholz wrote:
Whatever we decide, we should keep in mind that these libraries are
intended to be installed by copying over the real libraries. So it
would be real nice if xemacs did something reasonable (crashing is not
reasonable):
- if built on a system with athena3d libs, run on a system with athena.
- if built on a system with athena, run on a system with athena3d.
How do you intend that this is to be achieved?
AFAICT, the Xaw* library which XEmacs uses at run-time has to have the
same structure layouts as the Xaw* header files with which it was
built. I don't see any way around this.
--
Glynn Clements <glynn(a)sensei.co.uk>
8:39 a.m.
New subject: New Athena widget configuration (was Re: Problem with `configure --with-sound')
>>>> "Glynn" == Glynn Clements
<glynn(a)sensei.co.uk> writes:
Glynn> Martin Buchholz wrote:
> Whatever we decide, we should keep in mind that these libraries
are
> intended to be installed by copying over the real libraries. So it
> would be real nice if xemacs did something reasonable (crashing is not
> reasonable):
>
> - if built on a system with athena3d libs, run on a system with athena.
> - if built on a system with athena, run on a system with athena3d.
Glynn> How do you intend that this is to be achieved?
Glynn> AFAICT, the Xaw* library which XEmacs uses at run-time has to have the
Glynn> same structure layouts as the Xaw* header files with which it was
Glynn> built. I don't see any way around this.
If XEmacs only uses Xaw core functionality, it should compile, link
and run, with any combination of Xaw imposter header files and
libraries, if the Xaw cloners have done their job properly.
There is something to be said for `Just Working', even if ordinary Xaw
is kind of ugly.
Martin
9107
days inactive
9109
days old
4 comments
4 participants
participants (4)
-
Glynn Clements -
Jan Vroonhof -
Kyle Jones -
Martin Buchholz