From: Joseph Stewart <joseph.stewart@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Any demand for a supported Windows version of p9port?
Date: Wed, 27 Jul 2016 22:09:08 -0700 [thread overview]
Message-ID: <CANGQBe6fOkcs4CDzHF0d-+=f+Jt_OJJDsGFJzTie+uwKDYZpfQ@mail.gmail.com> (raw)
In-Reply-To: <84F7F989-9A31-4295-8A02-91A4EF65EA1A@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
Which version of MS Visual Studio would you use?
On Wed, Jul 27, 2016 at 6:41 PM, Winston Kodogo <kodogo@gmail.com> wrote:
> Hey Chris
>
> Cygwin is an option. Albeit one I wouldn’t use. The guys who did pf9 used
> mingw. Which I also wouldn’t use. I like MS Visual Studio with access to
> the native libraries on the platform of my choice - so colour me bigoted.
>
> I was kind of wondering if there was an option for people who like
> Microsoft development tools to build Plan9 tools, which are admittedly a
> minority taste in the Windows world, without spending several weeks
> installing 3rd party tools and then being told how stupid they are.
> > On 28/07/2016, at 1:27 PM, Chris McGee <sirnewton_01@yahoo.ca> wrote:
> >
> > I was thinking of using Cygwin to see would be capable of compiling p9p.
> >
> > Chris
> >
> >> On Jul 27, 2016, at 9:08 PM, Andrew Simmons <kodogo@gmail.com> wrote:
> >>
> >> What the subject line says.
> >>
> >> This is not remotely intended to disrespect Sean Quinlan’s 9pm, or the
> guys who did pf9. I’m just asking because there are still chunks of p9p
> that I’d like to have under Windows. Some of the chunks I want (mostly the
> command line utilities, also sam, not so much acme) I’ve managed to build
> under Microsoft Visual Studio (note to self - wash mouth out and learn to
> eschew IDEs and love mk ((also, sub-note to self, don’t use syntax
> highlighting)))
> >>
> >> But, and this is a large but, there are parts of p9port that seem to be
> dependent on the Unix world - unix pipes for one, the stuff about sigjmp
> for another.
> >>
> >> So, what the subject line says, but also - how much of the
> Unix-specific stuff in the current p9p is essential to a port to Windows?
> >>
> >> Go in peace
> >> James V Choate XXXVI
> >>
> >>
> >>
> >
> >
>
>
>
[-- Attachment #2: Type: text/html, Size: 2427 bytes --]
next prev parent reply other threads:[~2016-07-28 5:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 11:55 [9fans] Virtual Box 5.1 and Plan 9 Peter Hull
2016-07-27 23:59 ` cinap_lenrek
2016-07-28 1:08 ` [9fans] Any demand for a supported Windows version of p9port? Andrew Simmons
2016-07-28 1:27 ` Chris McGee
2016-07-28 1:41 ` Winston Kodogo
2016-07-28 5:09 ` Joseph Stewart [this message]
2016-07-28 5:34 ` Andrew Simmons
2016-07-28 8:39 ` hiro
2016-07-28 9:15 ` Staven
2016-07-28 23:53 ` Andrew Simmons
2016-07-28 10:49 ` Steve Simon
2016-07-29 0:03 ` Andrew Simmons
2016-07-28 6:34 ` [9fans] Virtual Box 5.1 and Plan 9 Matthew Veety
2016-07-28 8:36 ` hiro
2016-07-28 10:38 ` Peter Hull
2016-07-28 13:37 ` cinap_lenrek
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='CANGQBe6fOkcs4CDzHF0d-+=f+Jt_OJJDsGFJzTie+uwKDYZpfQ@mail.gmail.com' \
--to=joseph.stewart@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).