unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Nyacc patches for Mes to avoid bundling?
Date: Sun, 7 May 2017 07:16:02 -0700	[thread overview]
Message-ID: <70FFAE28-410D-4D1A-AF9C-21FC52C895C2@gmail.com> (raw)
In-Reply-To: <87k25t6r05.fsf@gnu.org>


> On May 7, 2017, at 12:54 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
> 
> Jan Nieuwenhuizen writes:
> 
>>> Maybe I can hack a `configure’ script together.
>> 
>> Great!  FWIW, I lifted build-aux/compile-all.scm from GuixSD to compile
>> the scheme files for Mes (mainly Nyacc).  You may want to look at
>> that/do that too.
> 
> I upgraded Mes to Nyacc 0.78.0 and I've added (basic) string-index,
> imported case-lambda from guile-1.8, and added #\cr short form for
> #\return to the reader.  Mes now runs vanilla Nyacc!
> 
> Now I'm testing to unbundle Nyacc from Mes. I just wrote some code to
> have `include-from-path' look in GUILE_LOAD_PATH...and to test it I
> haphazarly transplanted Mes' build system to nyacc
> 
>     https://gitlab.com/janneke/nyacc # wip-build
> 
> feel free to use or ignore any or all of it :-)
> 

I have released a 0.78.1 with the following additions:
1) configure
2) README.nyacc => README, INSTALL
3) Makefile.in 

You can perform the following to install only sources (does not require installed guile or guild):
  $ ./configure —site_scm_dir=/path/to/dest —site_scm_go_dir=/dummy
  $ make install-srcs

Matt




  reply	other threads:[~2017-05-07 14:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 17:59 Nyacc patches for Mes to avoid bundling? Jan Nieuwenhuizen
2017-05-04  0:07 ` Matt Wette
2017-05-05  2:09   ` Matt Wette
2017-05-05  6:07     ` Jan Nieuwenhuizen
2017-05-05 12:44       ` Matt Wette
2017-05-05 13:33         ` Jan Nieuwenhuizen
2017-05-05 22:59           ` Matt Wette
2017-05-06 15:21             ` Matt Wette
2017-05-06 16:00               ` Jan Nieuwenhuizen
2017-05-06 16:21                 ` Matt Wette
2017-05-06 16:33                   ` Jan Nieuwenhuizen
2017-05-07  7:54                     ` Jan Nieuwenhuizen
2017-05-07 14:16                       ` Matt Wette [this message]
2017-05-08 15:37                         ` Jan Nieuwenhuizen
2017-05-10 21:01                           ` Jan Nieuwenhuizen
2017-05-11  0:21                             ` Matt Wette
2017-05-12  3:52                               ` Matt Wette
2017-05-12  6:00                                 ` Jan Nieuwenhuizen
2017-05-12 15:10                                   ` Matt Wette
2017-05-05 13:19 ` Ludovic Courtès
2017-05-05 19:56   ` Jan Nieuwenhuizen
2017-05-05 20:22     ` Ludovic Courtès
2017-05-06 15:49       ` Jan Nieuwenhuizen

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=70FFAE28-410D-4D1A-AF9C-21FC52C895C2@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=janneke@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).