From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] windows port
Date: Fri, 25 Sep 2015 22:54:12 +0100 [thread overview]
Message-ID: <20150925215412.GG2254@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87bncqkye9.fsf@mushroom.localdomain>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
On Fri, Sep 25, 2015 at 02:00:14PM -0700, Chris Brannon wrote:
> Karl Dahlke <eklhad@comcast.net> writes:
>
> > Geoff is working on the windows port and making good progress.
>
> Woot! Yep, these are exciting times!
> So does this mean we'll be switching to cmake? If so, I should probably
> learn it.
Perhaps if this is working under visual studio.
Much as I'm not a huge cmake fan, it'll certainly make maintaining the build
easier compared to maintaining a makefile and visual studio project
separately.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-25 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 20:24 Karl Dahlke
2015-09-25 21:00 ` Chris Brannon
2015-09-25 21:54 ` Adam Thompson [this message]
2015-09-26 3:28 ` [Edbrowse-dev] html.c:757 Kevin Carhart
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=20150925215412.GG2254@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@the-brannons.com \
/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).