From: Steve Nickolas <usotsuki@buric.co>
To: Clem Cole <clemc@ccc.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Can I use Apout simulator on Windows 10?
Date: Thu, 15 Apr 2021 17:03:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2104151702260.15576@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CAC20D2OMRqAxVOgW818JU50EWE5DBYxo1gLv2Fj3AkP=-Du5oQ@mail.gmail.com>
On Thu, 15 Apr 2021, Clem Cole wrote:
> As its author, WKT has more info than others but since he does not mention
> it in his README and due to TZ issue (he's likely asleep right now), I'll
> take a shot. Note: I can not say I have tried it, but I would expect it
> to compile and run on WSL. I can say I ran in a few years ago on a Mac and
> 'just worked.' You might need to tweak it a little bit if for no other
> reason than RedHat Linux 2.2 is pretty old and was 32 bit, but WKT's code
> is pretty clean and I would not expect any real issues. Since he is
> assuming a 32-bit system, and I have not played with it in a while, my
> guess is that the one place you might need to be careful. His comment in
> the read says:
>
> It should compile on a 32-bit little-endian machine with
>
> some form of Unix; you may need to change some header file includes etc.
>
> See `defines.h' for the details. In particular, if your system doesn't have
>
> types for:
>
>
>
> int8_t, int16_t, int32_t, u_int8_t, u_int16_t, u_int32_t
>
> or if your compiler doesn't have char=1 byte, short= 2 bytes, int=4 bytes,
>
> then alter the relevant typedefs in `defines.h'.
Didn't someone here port apout to win32, and it *almost* worked 100%? I
remember reading about it on virtuallyfun.com, but I might be mistaken.
On Win10 you could also just install Debian in WSL, and it might work
better there?
-uso.
prev parent reply other threads:[~2021-04-15 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 18:21 Saif Resun
2021-04-15 20:29 ` Clem Cole
2021-04-15 21:03 ` Steve Nickolas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2104151702260.15576@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.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 NNTP newsgroup(s).