unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: P Pareit <pieter.pareit@planetinternet.be>
Subject: guile-doc-snarf replaced in the Makefile for scwm
Date: Tue, 10 Sep 2002 14:34:54 +0200	[thread overview]
Message-ID: <200209101434.54309.pieter.pareit@planetinternet.be> (raw)

Hey,

Sinds newer versions of guile do not provide guile-doc-snarf anymore and after 
the comments in guile-user I came up with the following solution:

This is the offending code in the original makefile:

.c.x:
	guile-doc-snarf $< $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $< > $@ \
	|| { rm $@; false; }
.cc.x:
	guile-doc-snarf $< $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $< > $@ \
	|| { rm $@; false; }
.c.doc:
	guile-doc-snarf $< $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $< > /dev/null \
        || { rm $@; false; }

An this is what I changed it to:

.c.x:
	guile-snarf $< $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $< > $@ \
	|| { rm $@; false; }
.cc.x:
	guile-snarf $< $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $< > $@ \
	|| { rm $@; false; }

Rational:

The documentation says to use guile-snarf to generate the .x files that gets 
included in the initializing functions.
This is because guile-doc-snarf used to first generate the documentation and 
then called guile-snarf, and so did the work of guile-snarf (see node Doc 
Snarfing in info).
For the .c.doc rule I was suggested to use guile-tools c2doc, but my 
installation did not include c2doc and I also did not find documentation for 
it. And the rule does not get used so I throw it out.

I also think it is not needed to remove the generated files if guile-snarf 
fails as guile-snarf will do when given file to output , so I could even 
change this to:

.c.x:
	guile-snarf $< -o $@ $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $<
.cc.x:
	guile-snarf $< -o $@ $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $<

If someone could confirm I'm right? This way I can start changing autogen.sh 
for scwm and send in a patch.

pieter;




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2002-09-10 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 12:34 P Pareit [this message]
2002-09-10 19:10 ` guile-doc-snarf replaced in the Makefile for scwm Marius Vollmer
2003-01-29 11:35   ` guile-mysql Sergey Dolin

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=200209101434.54309.pieter.pareit@planetinternet.be \
    --to=pieter.pareit@planetinternet.be \
    /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).