5:08 a.m.
The gtk-xemacs-21-2 branch now builds --with-gtk=yes, and will actually run
under the TTY (all hail the event loop!) The GTK stuff is much less
solid. It will briefly flash up the frame, then explode silently (or with
a silly dialog box if you have GNOME support compiled in).
If people want to check out the X and TTY side of this, to make sure the
lisp integration didn't cause anything to break, I would really appreciate
it.
-Bill P.
6:28 a.m.
New subject: Please, report builds with GTK ... = no; AIN'T-GOT-GTK PLATFORMS, TOO!
>>>> "-BP" == William M Perry
<wmperry(a)aventail.com> writes:
-BP> If people want to check out the X and TTY side of this, to
-BP> make sure the lisp integration didn't cause anything to
-BP> break, I would really appreciate it.
This is an official request from your Release Manager as well. This
applies to platforms where GTK is _not_ available as well as where GTK
_is_ available. It would be nice if you do this maybe twice/week until
we merge GTK into the mainline. (More details in a forthcoming status
report and announcement.)
------------------------------------------------------------------------
HOWTO getit:
Check out gtk-xemacs 21.2 from CVS as normal with the tag option
-r gtk-xemacs-21-2
(note this is a branch tag, and therefore will be sticky IIRC).
_Please_ send reports to xemacs-build-reports. Success/failure/WTF,
send 'em all.
------------------------------------------------------------------------
HOWTO reportit:
Just redirect make's output to beta.err, and use M-x build-report.
`build-report's docstring (actually, I've munged this heavily, so
don't get scared, Adrian ;-):
"Report build information including Installation and make output.
Prompts for status (usually SUCCESS or FAILURE). Then creates a mail
message with Subject header including status and version information,
using `compose-mail'. Point is left at the beginning of the mail
text. You may add some notes if you like and send the report.
Looks for Installation and the make output file (`beta.err' by
default, customizable via `build-report-make-output-files') in the
build directory of the running XEmacs by default (customizable via
`build-report-make-output-dir'). The output from make is filtered
through `build-report-keep-regexp' and `build-report-delete-regexp'
before being inserted in the message.
See also `mail-user-agent', `build-report-destination', and
`build-report-installation-file'."
NB: to actually read the docstrings for build-report-*, you'll need to
load build-report.el first.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
5:55 p.m.
>>>> "-BP" == William M Perry
<wmperry(a)aventail.com> writes:
-BP> The gtk-xemacs-21-2 branch now builds --with-gtk=yes
OK, I'm giong to start beating up on this. The first build I'm
actually going to do is my normal config + --with-gtk=no. I'll let
you know....
But I accidentally ran a config with the defaults, and I got Lucid
menubars and scrollbars, GTK dialogs, and Motif widgets. Huh?
-BP> if you have GNOME support compiled in
How do you get GNOME, again? is it autoconfiscated, or is there a
switch to control it?
eh-he-he, libglade support?
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
6:16 p.m.
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>> "-BP" == William M Perry
<wmperry(a)aventail.com> writes:
-BP> The gtk-xemacs-21-2 branch now builds --with-gtk=yes
OK, I'm giong to start beating up on this. The first build I'm
actually going to do is my normal config + --with-gtk=no. I'll let
you know....
Great, thanks! I don't think I've checked in the changes that break the X
build right now, so I will hold off for a while.
But I accidentally ran a config with the defaults, and I got Lucid
menubars and scrollbars, GTK dialogs, and Motif widgets. Huh?
Hrm - I'll bet that is just me being stupid in my configure tests - hang
on... yup. I'm a dumbass. Cut & paste got the better of me. How's the
attached patch?
-BP> if you have GNOME support compiled in
How do you get GNOME, again? is it autoconfiscated, or is there a switch
to control it?
It will be autodetected (if) when we remove the with_gnome=no chunk at the
beginning of configure.in. For now, you will have to manually specify
--with-gtk=yes --with-gnome=yes.
eh-he-he, libglade support?
Yup - pretty sweet. :)
(gtk-define-test
"Glade Interface" misc libglade t
(glade-init)
(glade-xml-get-type)
(let ((xml (glade-xml-new (expand-file-name "gtk-test.glade"
(gtk-test-directory))
nil)))
(setq window (glade-xml-get-widget xml "main_window"))
(glade-xml-signal-autoconnect xml)))
-Bill P.
6:34 a.m.
>>>> "-BP" == William M Perry
<wmperry(a)aventail.com> writes:
> OK, I'm giong to start beating up on this. The first build
I'm
> actually going to do is my normal config + --with-gtk=no. I'll
> let you know....
I got the gtk device specs in faces breakage. Debian unstable, Linux
2.2.18 system, no surprises. Will update and try again.
-BP> Great, thanks! I don't think I've checked in the changes
-BP> that break the X build right now, so I will hold off for a
-BP> while.
It's your pidgen. I want it in the release tarball too; use your best
judgement as to what will shake the bugs out fastest.
-BP> How's the attached patch?
Fixes, thank you. menubars, scrollbars = Lucid, dialogs, widgets =
Motif. Shudder. But that's the expected config.
-BP> For now, you will have to manually specify --with-gtk=yes
-BP> --with-gnome=yes.
Good, good.
A polite request: please don't _ask_ people to test the GTK stuff
itself until March 1. Many will, anyway, me, too, and I won't
discourage them.
But the primary purpose over the next few weeks will getting the
_supported_ code in shape. I won't hesitate to postpone introduction
of GTK until the next release, or rip it bleeding out of the release
tarball, if I think it threatens stability of other code. That's not
good for GTK.
> eh-he-he, libglade support?
-BP> Yup - pretty sweet. :)
Good, saves me doing it (badly :-]). But don't tell Jamie Zawinski
about it yet; I want to see his face when he hears about it. Jeez, an
open source project doing something that works _for_ the users for
once. :-)
Betcha we have Custom/GTK that rocks by the September release with
libglade in there. Almost makes me want to volunteer to run it.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
8693
days inactive
8694
days old
4 comments
2 participants
participants (2)
-
Stephen J. Turnbull -
William M. Perry