all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: build failure [Re: bug#17673: 24.4.50; trunk r117239 build failure on Windows]
Date: Tue, 03 Jun 2014 22:16:06 +0400	[thread overview]
Message-ID: <538E10E6.8020708@yandex.ru> (raw)
In-Reply-To: <dpwqcxq3sk.fsf@fencepost.gnu.org>

On 06/03/2014 09:52 PM, Glenn Morris wrote:

> Note this old comment in configure.ac:
>
> dnl Don't set this for GTK.  A lot of tests below assumes Xt when
> dnl USE_X_TOOLKIT is set.
>              USE_X_TOOLKIT=none ;;
>
> So it was intentional that libXt-devel has not been required in gtk
> builds till now.

So, utterly crappy lwlib interface forces us to choose one from:

1) require libXt-devel even for GTK build and have lwlib stubs
    in src/menu.h (for HAVE_NTGUI), or

2) do not require libXt-devel for GTK build, but have even more
    lwlib stubs in src/gtkutil.[ch] (as it was before r117239).

What about an idea to really port lwlib enough to avoid stubs at all?

Dmitry




  reply	other threads:[~2014-06-03 18:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 15:11 build failure [Re: bug#17673: 24.4.50; trunk r117239 build failure on Windows] Stephen Berman
2014-06-03 16:04 ` Eli Zaretskii
2014-06-03 16:13   ` Eli Zaretskii
2014-06-03 16:41     ` Stephen Berman
2014-06-03 17:02       ` Eli Zaretskii
2014-06-03 17:13         ` Eli Zaretskii
2014-06-03 17:24           ` Dmitry Antipov
2014-06-03 17:29         ` Dmitry Antipov
2014-06-03 17:52           ` Glenn Morris
2014-06-03 18:16             ` Dmitry Antipov [this message]
2014-06-03 18:51           ` Stephen Berman
2014-06-03 20:02             ` Paul Eggert
2014-06-03 21:02               ` Eli Zaretskii
2014-06-03 21:12               ` Stephen Berman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=538E10E6.8020708@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.