unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Mike Gran" <spk121@yahoo.com>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: guile-user@gnu.org
Subject: Re: My Lisp Game Jam entry
Date: Tue, 1 May 2018 19:13:00 -0700	[thread overview]
Message-ID: <20180502021300.GA1606@joshua.dnsalias.com> (raw)
In-Reply-To: <87zi1j3zum.fsf@web.de>

On Tue, May 01, 2018 at 10:03:53PM +0200, Arne Babenhauserheide wrote:
> 
> I built and ran it from source and liked it a lot!

Thanks.

> 
> Does this work *reliably* on Windows? I???ve been suffering from a hard
> time to ship games for Windows, and if you???ve solved that, this would be
> a huge step forward (for me)!

The Windows build seems quite reliable, but, what I ended up doing was
making a static build of libguile that incorporated a static build of
all its dependencies.  That build is 32-bit only, with no threads, using
a version of gc compiled with its default static makefile.

The 32-bit is necessary, because Guile expects sizeof(void*) == sizeof(long)
as a hard requirement.

That static build is likely unnecessary, but, I did it that way to make
debugging easier.

The null threads is currently necessary.  There is some sort of mutex
lock in the GC when Guile is compiled with libwinpthreads.  It actully
runs when built with libwinpthreads, but, locks up on cleanup,
especially when smobs are present. I didn't have time to debug it.

You can see the script I used to build a static Guile with its
dependencies in https://github.com/spk121/psychic-guacamole/
I built it using the msys2 flavor of mingw32.

> 
> Best wishes,
> Arne

Regards,
Mike





      reply	other threads:[~2018-05-02  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 15:13 My Lisp Game Jam entry Mike Gran
2018-04-30 15:21 ` Mike Gran
2018-05-01 20:03 ` Arne Babenhauserheide
2018-05-02  2:13   ` Mike Gran [this message]

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=20180502021300.GA1606@joshua.dnsalias.com \
    --to=spk121@yahoo.com \
    --cc=arne_bab@web.de \
    --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).