unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-devel@gnu.org
Subject: Re: ttn's build system
Date: Wed, 10 Mar 2004 19:59:32 +0100	[thread overview]
Message-ID: <87wu5sbka3.fsf@ivanova.rotty.yi.org> (raw)
In-Reply-To: 87n06uvuy4.fsf@ivanova.rotty.yi.org

Andreas Rottmann <a.rottmann@gmx.at> writes:

>> Is there any chance of mainline Guile using the extended -e stuff or
>> accepting patches to use ttn's nice build system and extended
>> guile-config stuff? I am willing to chunk out anything from Guile
>> 1.4.x that would be useful to the official Guile branch if there
>> aren't any copyright issues / the patches will be accepted. 
>>
> Have you already started this? I'm especially interested in the
> build-system, and will break that out into a separate piece, since I
> intend to use it for the Guile-Library thing and possible at a later
> point in Guile-Gnome. I can't wait for this being perhaps eventually
> integrated into Guile (I suspect this might take *some* time to
> happen). So if you haven't started tackling "porting" the build
> system, it *might* make sense to wait for what I'll produce, which
> will be a piece of software building on Guile, but not integrated into
> guile-tools. This means just shipping it with Guile in the future,
> making guile-tools tie it in, could be an alternative of a direct
> port, avoiding duplicate effort.
>
Mostly ignore the above. My current aproach will make use of
autofrisk, but not break it out or change it. However, I'm not even
sure it will work as in Guile 1.7, as guile-tools read-scheme-source
is broken (omits forms under some conditions). So any work to patch
autofrisk and the related tools like read-scheme-source is highly
appreciated and will happily be merged into the ttn-features branch of
my unofficial archive.

Cheers, Andy
-- 
Andreas Rottmann         | Rotty@ICQ      | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

The best way to accelerate a Windows machine is at 9.81 m/s^2



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


  parent reply	other threads:[~2004-03-10 18:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01  3:32 Extended -e syntax Clinton Ebadi
2004-03-01  5:04 ` Andreas Rottmann
     [not found]   ` <E1AxlJY-0002cb-00@surf.glug.org>
2004-03-01 14:27     ` Arch and Guile Andreas Rottmann
2004-03-01 19:04       ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14         ` ITLA Andreas Rottmann
2004-03-01 21:55           ` ITLA Tom Lord
2004-03-02  0:11             ` ITLA Andreas Rottmann
2004-03-02  2:50               ` ITLA Tom Lord
2004-03-02 14:04                 ` ITLA Andreas Rottmann
2004-03-02  3:26             ` ITLA Miles Bader
2004-03-03 11:22           ` ITLA Neil Jerram
2004-03-03 11:55             ` ITLA Andreas Rottmann
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
     [not found]   ` <E1AziNk-0007mW-00@surf.glug.org>
2004-03-06 20:39     ` ttn's build system Andreas Rottmann
2004-03-10 18:59   ` Andreas Rottmann [this message]
2004-03-10 22:28   ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22   ` Tom Lord

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=87wu5sbka3.fsf@ivanova.rotty.yi.org \
    --to=a.rottmann@gmx.at \
    --cc=guile-devel@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).