From: fig <type9freak@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Porting software from other operating systems (Namely Mac OS 9) to Plan 9
Date: Sun, 13 Nov 2022 11:56:53 -0800 [thread overview]
Message-ID: <CANF_3RgPHOzp7EsBunGb9h7S7fZqFAPCmk1S2SyAFT_jYKw5cg@mail.gmail.com> (raw)
In-Reply-To: <16683546150.A5398.97827@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]
hi radiuspi,
here are a few links about porting to plan 9. hopefully these are helpful
for you as they are to me. you did not mention 9front, so if you don’t know
about it i recommend learning about it, as it provides many helpful
programs you don’t have in 9legacy. the third link is a man page for the
coding style of 9front, which may be helpful for rewriting that C++ and obj
C.
https://plan9.io/wiki/plan9/Porting_alien_software_to_Plan_9/index.html
http://wiki.9front.org/porting
http://man.9front.org/6/style
On Sun, Nov 13, 2022 at 7:50 AM <radiuspi314@gmail.com> wrote:
> Hello all! Nightdive Studios recently released the source code for the Mac
> OS9 / PowerPC version of System Shock 1. Besides being among my favorite
> games, it's also one of the first properly 3D games to exist, and getting
> it running on Plan 9 would be a fun and interesting project in my
> estimation. The source code (https://github.com/NightDive-Studio/shockmac)
> is written in C for the most part, with the notable exception of a bit of
> C++ and the tiniest sliver of objective-c, each of which is possible to
> convert somewhat inelegantly back into ansi C. It has conveniently
> separated out the portion of the code that is specific to Mac, so my
> admittedly uninformed hope is that if I could simply modify this code and
> replace any references to Mac OS 9 event handlers and resources, I could
> compile it on plan 9. Are there any resources available to port these
> event handlers or resources, or any known projects that span across mac os
> 9 and plan 9, that I could use as references?
>
> Apologies as well if this topic had already been created; after a brief
> search, I couldn't find any other questions asking this same thing, so I
> figured I'd produce my own and if I had missed something in my search
> someone might point me in the right direction.
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Tfd89dd5bd6825f5c-M6c7a04baddeb544ee29ab673>
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tfd89dd5bd6825f5c-Madeef7f2afb550d041fc4d19
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3324 bytes --]
next prev parent reply other threads:[~2022-11-13 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 15:50 radiuspi314
2022-11-13 19:56 ` fig [this message]
2022-11-13 22:12 ` Amanda Stjerna
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=CANF_3RgPHOzp7EsBunGb9h7S7fZqFAPCmk1S2SyAFT_jYKw5cg@mail.gmail.com \
--to=type9freak@gmail.com \
--cc=9fans@9fans.net \
/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).