From: Sven Luther <sven.luther@wanadoo.fr>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
mgushee@havenrock.com, caml-list@inria.fr
Subject: Re: [Caml-list] OpenGL support in LablGTK2?
Date: Wed, 8 Dec 2004 16:50:31 +0100 [thread overview]
Message-ID: <20041208155031.GA19793@pegasos> (raw)
In-Reply-To: <20041208153837.GA19423@pegasos>
On Wed, Dec 08, 2004 at 04:38:37PM +0100, Sven Luther wrote:
> On Wed, Dec 08, 2004 at 10:53:15PM +0900, Jacques Garrigue wrote:
> > From: Sven Luther <sven.luther@wanadoo.fr>
> > > > Now, it seems that the gtk people have botched something, and gtkglarea
> > > > have stopped working. If this is not solved soon, I suppose lablgtk2
> > > > will have to move to gtkglext, and emulate gtkglarea on top of it (you
> > > > don't want API changes, do you?)
> > >
> > > Notice that this is not really true, look at the debian lablgtk2 package, it
> > > builds against lablgl, and everything works fine.
> > >
> > > Well, at least the GL examples work with lablgtk2. Lablgtk2 uses the
> > > libgtkgl2.0-dev package instead of the older gtkglarea ones though, but it
> > > seems to be the same stuff :
> >
> > As far as I can see, what you call libgtkgl2.0 happens to be what
> > others call gtkglarea-1.99, i.e. the gtk2-ized version of gtkglarea.
> > It seems that we are a few here experiencing problems with this
> > version and very recent versions of gtk2 (in my case, gtk-2.4.13).
> > So maybe you are not using the same version of gtk, or the debian
> > people have already solved the problem, or actually the cause is
> > different altogether (hard to guess).
>
> Well :
>
> $ dpkg -l | grep libgtk2.0-0
> ii libgtk2.0-0 2.4.13-1 The GTK+ graphical user interface library
>
> But we have probably not rebuilded lablgtk or gtkglarea with it recently, let
> me check ...
>
> gtkgl2 (1.99.0-2) unstable; urgency=low
>
> ...
>
> -- Marcelo E. Magallon <mmagallo@debian.org> Sun, 11 May 2003 19:47:24 +0200
>
> So, maybe there is a build problem, let me check and rebuild it locally to be
> sure.
>
> What exactly are the problems ? During the build of libgtkgl2, or during the
> build of lablgl ?
Both gtkgl2 and lablgl build without problems, so you may well want to look at
the debian packages for the source of your problem. (Or simply run debian).
Friendly,
Sven Luther
next prev parent reply other threads:[~2004-12-08 15:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 22:21 Matt Gushee
2004-12-07 0:28 ` [Caml-list] " Olivier Andrieu
2004-12-07 1:11 ` Matt Gushee
2004-12-07 9:51 ` Olivier Andrieu
2004-12-07 18:30 ` Matt Gushee
2004-12-07 21:36 ` Sven Luther
2004-12-08 0:33 ` Jacques Garrigue
2004-12-08 1:03 ` Matt Gushee
2004-12-08 10:03 ` Sven Luther
2004-12-08 13:53 ` Jacques Garrigue
2004-12-08 15:38 ` Sven Luther
2004-12-08 15:50 ` Sven Luther [this message]
2004-12-08 20:34 ` Grégory Guyomarc'h
2004-12-09 0:36 ` Jacques Garrigue
2004-12-09 14:17 ` Sven Luther
2004-12-24 1:56 ` Jacques Garrigue
2004-12-30 7:32 ` Matt Gushee
2004-12-31 9:30 ` Jacques Garrigue
2005-01-27 5:16 ` Matt Gushee
2005-01-27 7:59 ` Jon Harrop
2005-01-27 10:24 ` Jon Harrop
2004-12-07 10:10 ` malc
2004-12-07 15:30 ` briand
2004-12-07 18:24 ` Matt Gushee
2004-12-07 18:48 ` Blair Zajac
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=20041208155031.GA19793@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=mgushee@havenrock.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).