unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Guile and MS-Windows on Major Govt. Project...
Date: Fri, 28 Jun 2002 10:11:53 +0200	[thread overview]
Message-ID: <878z4z960m.fsf@peder.flower> (raw)

David Lane writes:

> ... I have gotten Guile 1.5.6 to build under Cygwin.

That's great.

> The end result is a DLL version (guile.exe is about 4K); presumably it's
> simpler to get it all statically built.

There were quite some issues building it statically, because the Guile
config and build process seems to be ill prepared for cross
compilation; it tries to run cross-compiled binaries.  Anyone working
on that, btw, or would you take a patch?

> I have a unified diff but it's about 3MB since it includes the files that
> get created by auto* (Makefile, Makefile.in, configure, etc).

I'm rather interested in that, would you send me your full patch?

Greetings,     
Jan.     

Btw:
  It should be real easy to exclude the autogenerated stuff, just
  do something like

     diff -purN --exclude=Makefile.in --exclude=configure ../guile.orig/ .

  and of course a 'make realclean' first in both directories.  Once
  you get it down to a reasonable size, you can post your stripped
  patch here too, if you like.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org


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


             reply	other threads:[~2002-06-28  8:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28  8:11 Jan Nieuwenhuizen [this message]
2002-06-28 22:14 ` Guile and MS-Windows on Major Govt. Project David Lane
     [not found] <3D1B1DCD.7090500@bitmead.com>
2002-06-28  1:49 ` Bruce Korb
     [not found] ` <3D1BC0B9.282F1F21@pacbell.net>
2002-06-28  5:51   ` Chris Bitmead
     [not found]   ` <3D1BF96A.1030101@bitmead.com>
2002-06-29  2:01     ` Christopher Cramer
2002-07-01  3:46     ` Clinton Ebadi
     [not found]     ` <200206302346.11902.unknown_lamer@unknownlamer.org>
2002-07-01 23:09       ` Chris Bitmead
     [not found]       ` <3D20E140.6050003@bitmead.com>
2002-07-02  1:13         ` Clinton Ebadi
2002-07-02 14:41           ` Chris Bitmead
     [not found]           ` <3D21BBB0.6000302@bitmead.com>
2002-07-02 15:29             ` Ken Anderson
     [not found]           ` <5.0.2.1.2.20020702112242.00b16ad0@zima.bbn.com>
2002-07-03 12:47             ` Chris Bitmead
     [not found]             ` <5.0.2.1.2.20020703085953.026d4b80@zima.bbn.com>
2002-07-03 14:10               ` Chris Bitmead
     [not found]             ` <3D22F264.9010502@bitmead.com>
2002-07-03 13:27               ` Ken Anderson
2002-07-05 20:21               ` Per Bothner
     [not found]               ` <3D25FFB4.9060500@bothner.com>
2002-07-06  2:30                 ` Chris Bitmead
     [not found]                 ` <3D265661.9030201@bitmead.com>
2002-07-06 22:11                   ` Ken Anderson
2002-07-08 21:53                     ` Christopher Cramer
2002-07-07 15:35                   ` Per Bothner
  -- strict thread matches above, loose matches on Subject: below --
2002-06-27 14:14 Chris Bitmead

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=878z4z960m.fsf@peder.flower \
    --to=janneke@gnu.org \
    --cc=guile-user@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.
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).