From: Geoff McLane <ubuntu@geoffair.info>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Windows MSVC140 build
Date: Fri, 27 Jan 2017 20:43:16 +0100 [thread overview]
Message-ID: <78e0ac32-8802-b381-10df-a27474a84d7d@geoffair.info> (raw)
In-Reply-To: <20170027142149.eklhad@comcast.net>
Hi Karle,
Thanks for the quick reply...
1. Ok, 'size_t' would also be ok, I think... just not 'ssize_t', which
is not defined...
2. Yes, it seems msvc140 wants a prototype spade cast as a spade, not a
'short ... *', like it may in fact be ;=))
Just brought my fork 100% up to current repo, and find some other errors.
3 unresolved - ftruncate, truncate, and usleep, so need to look at
these tomorrow, or soonest...
Meantime have pushed my current changes to a 'msvc140-32' branch in my
fork...
Be back soon...
Regards, Geoff.
next prev parent reply other threads:[~2017-01-27 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 19:02 Geoff McLane
2017-01-27 19:21 ` Karl Dahlke
2017-01-27 19:43 ` Geoff McLane [this message]
2017-01-27 19:59 ` Karl Dahlke
2017-01-28 2:06 ` Geoff McLane
2017-01-28 2:36 ` Karl Dahlke
2017-01-28 16:53 ` Geoff McLane
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=78e0ac32-8802-b381-10df-a27474a84d7d@geoffair.info \
--to=ubuntu@geoffair.info \
--cc=edbrowse-dev@lists.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).