public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Bo Forslund <bo.forslund@abc.se>
To: Steve Tell <tell@telltronics.org>
Cc: guile-gtk list <guile-gtk@sourceware.cygnus.com>
Subject: Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)
Date: Fri, 16 Nov 2001 14:11:00 -0000	[thread overview]
Message-ID: <3C2D128D.36581FC5@abc.se> (raw)
In-Reply-To: <Pine.LNX.4.21.0112280922590.26555-100000@ariel.lan.telltronics.org>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

Steve Tell wrote:

> On Thu, 27 Dec 2001, Steve Tell wrote:
> To followup my own question, it seems that CVS guile-gtk as of last night
> doesn't really need gnome-common and pkgconfig; running the traditional
> autogen procedure, "aclocal; automake --add-missing-gnu; autoheader; autoconf"
> enables it to configure and build.
>

This is what I do in the  rpm package. ( or at least what I intended to heh... )
I did it live in the BUILD dir and everything worked nice.  But I couldn't get
the rpm working until I realized that forgot to add the lines to the spec file.
The testing tree of guile-gtk worked but the rpm version did not. It was a bit
tricky to keep track of which version was running.

I almost believed in ghosts for a while. =)

here is a source rpm
/home/bo/tmp/guile-gtk-20011121-7.src.rpm

The patch used in the rpm comes as an attach.
guile-gtk-20011121/Makefile.am  and  guile-gtk-20011121/examples/configure.in are
changed.

Bo

[-- Attachment #2: guile-gtk-20011121-5.patch --]
[-- Type: text/plain, Size: 2745 bytes --]

diff -Nur guile-gtk-20011121-virgin/Makefile.am guile-gtk-20011121/Makefile.am
--- guile-gtk-20011121-virgin/Makefile.am	Tue Nov 13 00:06:08 2001
+++ guile-gtk-20011121/Makefile.am	Fri Dec 28 22:39:15 2001
@@ -1,26 +1,20 @@
 # -*- Makefile -*-
 
-autoconf_macros = gnome-guile-checks.m4
-acinclude.m4: $(autoconf_macros)
-	cd $(srcdir); \
-	cat $(autoconf_macros) > acim.tmp; \
-	mv acim.tmp acinclude.m4
-
-#bin_PROGRAMS    = $(GUILE_GTK_VERSION)
+bin_PROGRAMS    = $(GUILE_GTK_VERSION)
 bin_SCRIPTS     = build-guile-gtk
 lib_LTLIBRARIES = $(LIBGUILEGTK_VERSION) $(LIBGUILEDLOPENHELPER)
 
-#EXTRA_PROGRAMS = guile-gtk-1.2 guile-gtk-1.3
+EXTRA_PROGRAMS = guile-gtk-1.2 guile-gtk-1.3
 EXTRA_LTLIBRARIES = libguilegtk-1.2.la libguilegtk-1.3.la \
                     libguiledlopenhelper.la
 
-#guile_gtk_1_2_SOURCES = main.c
-#guile_gtk_1_2_LDFLAGS = -export-dynamic
-#guile_gtk_1_2_LDADD = libguilegtk-1.2.la $(GUILE_LIBS) $(GTK_LIBS)
-
-#guile_gtk_1_3_SOURCES = main.c
-#guile_gtk_1_3_LDFLAGS = -export-dynamic
-#guile_gtk_1_3_LDADD = libguilegtk-1.3.la $(GUILE_LIBS) $(GTK_LIBS)
+guile_gtk_1_2_SOURCES = main.c
+guile_gtk_1_2_LDFLAGS = -export-dynamic
+guile_gtk_1_2_LDADD = libguilegtk-1.2.la $(GUILE_LIBS) $(GTK_LIBS)
+
+guile_gtk_1_3_SOURCES = main.c
+guile_gtk_1_3_LDFLAGS = -export-dynamic
+guile_gtk_1_3_LDADD = libguilegtk-1.3.la $(GUILE_LIBS) $(GTK_LIBS)
 
 INCLUDES = $(GTK_CFLAGS) -I$(includedir) $(GUILE_INCS)
 
@@ -68,9 +62,9 @@
 
 include_HEADERS = guile-gtk.h
 
-#install-exec-local:
-#	mkdir -p $(bindir)
-#	cd $(bindir) && rm -f guile-gtk && $(LN_S) $(GUILE_GTK_VERSION) guile-gtk
+install-exec-local:
+	mkdir -p $(bindir)
+	cd $(bindir) && rm -f guile-gtk && $(LN_S) $(GUILE_GTK_VERSION) guile-gtk
 
 gtkmoduledir = $(datadir)/guile/gtk
 vgtkmoduledir = $(datadir)/guile/gtk-$(GTK_VERSION)
@@ -109,8 +103,8 @@
 gdk-glue.c: $(gdkdefs) build-guile-gtk
 	$(BUILD) -I $(srcdir) glue $(gdkdefs) >tmpd && mv tmpd $@
 
-#main.c:  $(gtkdefs) $(gdkdefs) build-guile-gtk
-#	$(BUILD) -I $(srcdir) main $(gtkdefs) $(gdkdefs) >tmpm && mv tmpm $@
+main.c:  $(gtkdefs) $(gdkdefs) build-guile-gtk
+	$(BUILD) -I $(srcdir) main $(gtkdefs) $(gdkdefs) >tmpm && mv tmpm $@
 
 Makefile: $(BUILT_SOURCES)
 
diff -Nur guile-gtk-20011121-virgin/examples/configure.in guile-gtk-20011121/examples/configure.in
--- guile-gtk-20011121-virgin/examples/configure.in	Sat Dec  2 13:10:27 2000
+++ guile-gtk-20011121/examples/configure.in	Fri Dec 28 22:42:41 2001
@@ -5,14 +5,6 @@
 AC_PROG_CC
 AM_PROG_LIBTOOL
 
-GNOME_COMMON_INIT
-GNOME_PLATFORM_GNOME_2(no)
-
-if test $platform_gnome_2 = yes ; then
-  GNOME_PKGCONFIG_CHECK_MODULES(GTK, gtk+-2.0:1.3.1)
-else
-  GNOME_PKGCONFIG_CHECK_MODULES(GTK, gtk+:1.2.6)
-fi
 AC_SUBST(GTK_CFLAGS)
 AC_SUBST(GTK_LIBS)
 

WARNING: multiple messages have this Message-ID
From: Bo Forslund <bo.forslund@abc.se>
To: Steve Tell <tell@telltronics.org>
Cc: guile-gtk list <guile-gtk@sourceware.cygnus.com>
Subject: Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)
Date: Fri, 28 Dec 2001 16:47:00 -0000	[thread overview]
Message-ID: <3C2D128D.36581FC5@abc.se> (raw)
Message-ID: <20011228164700.kBfcRyLXHVDa1PaHQrLBxVyhsbOu0h6GjQzPT-odON0@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0112280922590.26555-100000@ariel.lan.telltronics.org>

Steve Tell wrote:

> On Thu, 27 Dec 2001, Steve Tell wrote:
> To followup my own question, it seems that CVS guile-gtk as of last night
> doesn't really need gnome-common and pkgconfig; running the traditional
> autogen procedure, "aclocal; automake --add-missing-gnu; autoheader; autoconf"
> enables it to configure and build.
>

This is what I do in the  rpm package. ( or at least what I intended to heh... )
I did it live in the BUILD dir and everything worked nice.  But I couldn't get
the rpm working until I realized that forgot to add the lines to the spec file.
The testing tree of guile-gtk worked but the rpm version did not. It was a bit
tricky to keep track of which version was running.

I almost believed in ghosts for a while. =)

here is a source rpm
/home/bo/tmp/guile-gtk-20011121-7.src.rpm

The patch used in the rpm comes as an attach.
guile-gtk-20011121/Makefile.am  and  guile-gtk-20011121/examples/configure.in are
changed.

Bo

  reply	other threads:[~2001-12-29  0:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  4:34 ERROR: In procedure dynamic-link: Bo Forslund
2001-10-11  6:16 ` Alexey Rodriguez Y
2001-10-11 13:25   ` Bo Forslund
2001-10-11 15:20     ` Alexey Rodriguez Y
2001-10-18  0:23       ` Bo Forslund
2001-10-18  3:10         ` Marius Vollmer
2001-10-18 10:59           ` Alexey Rodriguez Y
2001-10-19 15:01             ` Bo Forslund
2001-11-05 17:33               ` Marius Vollmer
2001-11-12 13:11                 ` Bo Forslund
2001-11-14 10:53                   ` Marius Vollmer
2001-11-12 14:08             ` Marius Vollmer
2001-11-14 20:24               ` Alexey Rodriguez Y
2001-11-15  5:28                 ` Marius Vollmer
2001-11-15  7:11                   ` Bo Forslund
2001-11-15 15:20                     ` guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:) Steve Tell
2001-11-15 15:39                       ` Steve Tell
2001-11-16 14:11                         ` Bo Forslund [this message]
2001-11-17  6:17                           ` Bo Forslund
2001-11-18  8:30                             ` Yet a new version " Bo Forslund
2001-12-28 20:21                               ` Bo Forslund
2001-12-28 17:07                             ` guile-gtk snapshot " Bo Forslund
2001-12-28 16:47                           ` Bo Forslund
2001-12-28  6:25                         ` Steve Tell
2001-11-25  5:33                       ` Ariel Rios
2001-12-30 23:39                         ` Ariel Rios
2001-12-27 20:28                       ` Steve Tell
2001-11-25  7:33                     ` ERROR: In procedure dynamic-link: Bo Forslund

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=3C2D128D.36581FC5@abc.se \
    --to=bo.forslund@abc.se \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=tell@telltronics.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).