From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: GTK patches part 1
Date: Mon, 9 Dec 2002 17:27:31 +0100 (MET) [thread overview]
Message-ID: <200212091622.gB9GMw16022638@stubby.bodenonline.com> (raw)
In-Reply-To: <87znrfuucc.fsf@wesley.springies.com> from "Alan Shutko" at dec 09, 2002 09:42:43
>
> Miles Bader <miles@gnu.org> writes:
>
> > --with-x-toolkit is better though, because it makes explicit the fact that
> > GTK and the other supported toolkits are mutually exclusive. Perhaps the
> > programs you're thinking of can only use one GUI toolkit, which is enabled
> > using --with-gtk?
>
> One important thing about --with-gtk is that it's really
> --with-gtk=/path, which allows you to specify which gtk to use.
> (--with-gtk is a degenerate case which says use gtk wherever you can
> find it.)
>
> Maybe --with-gtk should continue to specify where to find gtk, and
> --with-x-toolkit=gtk can turn on gtk? But it seems annoying to have
> to specify --with-x-toolkit=gtk if you're already specifying a gtk
> path.
What I saw from gnome2 and the likes, the preferred thing seems to use
--with-pkg-config-prog=/path/to/pkg_config and get the paths from that
program. I've added --with-pkg-config-prog in configure.in.
I think that --with-gtk=/path was the GTK 1.x way to specify paths. GTK 2.x
requires pkg_config. pkg_config is a bit easier to handle, as it
sets all the libraries, ldflags and cflags correct, as opposed to have
configure look for required libraries.
Jan D.
next prev parent reply other threads:[~2002-12-09 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 19:19 GTK patches part 1 Jan D.
2002-12-09 5:14 ` Miles Bader
2002-12-09 12:44 ` Jan D.
2002-12-09 13:20 ` Miles Bader
2002-12-09 14:42 ` Alan Shutko
2002-12-09 15:24 ` Miles Bader
2002-12-09 16:27 ` Jan D. [this message]
2002-12-10 21:30 ` Richard Stallman
2002-12-09 16:21 ` Jan D.
2002-12-09 13:23 ` Andreas Schwab
2002-12-09 17:25 ` Jan D.
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=200212091622.gB9GMw16022638@stubby.bodenonline.com \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@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.