GNU bug report logs - #31672
[PATCH 0/2] Add Mame

Previous Next

Package: guix-patches;

Reported by: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>

Date: Thu, 31 May 2018 19:41:01 UTC

Severity: normal

Tags: patch

Done: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Rutger Helling <rhelling <at> mykolab.com>
Cc: 31672 <at> debbugs.gnu.org
Subject: [bug#31672] [PATCH 0/2] Add Mame
Date: Sat, 02 Jun 2018 19:57:41 +0200
Correcting myself,

Nicolas Goaziou <mail <at> nicolasgoaziou.fr> writes:

> +               ;; Create "mame" executable.  MAME expects to be called from
> +               ;; the directory where the "mame64" directory lives.  Since we
> +               ;; cannot afford to do that, we start a sub-shell in the
> +               ;; appropriate directory.
> +               (let* ((bin (string-append out "/bin"))
> +                      (script (string-append bin "/mame")))
> +                 (mkdir-p bin)
> +                 (with-output-to-file script
> +                   (lambda _
> +                     (format #t
> +                             "#!~a\n~a/mame64 -inipath ~a/mame \"$@\"~%"
> +                             (which "sh") share share)))

Oops. Wrong patch. I meant:

                 (with-output-to-file script
                   (lambda _
                     (format #t
                             "#!~a\n(cd ~a/share/mame && exec ./mame64 \"$@\"~%"
                             (which "sh") share)))

Anyway, this is not totally satisfactory because one cannot use, e.g.,
"mame -createconfig" and have ini files generated in current directory.

I don't know how to fix that issue.




This bug report was last modified 7 years and 40 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.