unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Mark H Weaver <mhw@netris.org>
Cc: Mark Sutton <aeizon.jm@gmail.com>, 14080@debbugs.gnu.org
Subject: bug#14080: Guile bug building from source with pkg-config
Date: Sat, 30 Mar 2013 22:04:19 -0300	[thread overview]
Message-ID: <20130330220419.502d3b30@capac> (raw)
In-Reply-To: <87boa079t2.fsf@tines.lan>

Hello Mark(s) :)

> Also, what version of g-wrap are you trying to build?

Note that in order to build guile-clutter, you also need the following dependencies
to be satisfied [i'm using git, so this is an extract from the README file of the
clutter branch of guile-gnome-platform]

	Guile-Clutter requires Clutter 1.10 development packages.

	Guile-Clutter depends on some parts of Guile-GNOME: the GLib, ATK,
	Pango, and Cairo wrapsets.  These are commonly distributed with the
	`guile-gnome-platform' tarball.  The Guile-GNOME platform tarball itself
	depends on G-Wrap and Guile-Cairo.  See http://gnu.org/s/guile-gnome/,
	for more information.

Note that you will need the very latest guile-cairo [i mean and recommend a git
clone, because it's been patched by Andy Wingo [the developer] in oder to run the
'bouncer' example I wrote [based on the same example written in C by the clutter
folks] and I don't think Andy did get the time to create a new guile-cairo tarball.

If you need [more] help, let me know.

Cheers,
David





  reply	other threads:[~2013-03-31  1:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  8:11 bug#14080: Guile bug building from source with pkg-config Mark Sutton
2013-03-30  7:21 ` Mark H Weaver
     [not found]   ` <51574E20.5080209@gmail.com>
2013-03-30 23:10     ` Mark H Weaver
2013-03-30 23:22       ` Mark H Weaver
2013-03-31  1:04         ` David Pirotte [this message]
2013-03-31 12:16         ` Mark Sutton
2016-06-20 20:26 ` Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=20130330220419.502d3b30@capac \
    --to=david@altosw.be \
    --cc=14080@debbugs.gnu.org \
    --cc=aeizon.jm@gmail.com \
    --cc=mhw@netris.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).