edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  Windows MSVC140 build
Date: Fri, 27 Jan 2017 21:36:23 -0500	[thread overview]
Message-ID: <20170027213623.eklhad@comcast.net> (raw)
In-Reply-To: <7d547421-eb32-0e29-b674-c07079b60659@geoffair.info>

> Pushed a quick fix to -
> https://github.com/geoffmcl/edbrowse/tree/msvc140-32

Ok, not sure how to access or apply this.
I think you still have permissions on our branch, so you can go ahead and push your changes, they seem fine to me.

> not sure I understood the use of 'ftruncate' in the second case...

It should have been cacheControl, a bug, I have fixed it now.
This code only compiles, has not been tested at all.
Chris still has to write the part that connects it to the http engine.
So for now it's just there.
That's ok, you can make sure it builds on windows.
We'll need to test it eventually,
in windows I put the cache directory down in the user specific temp area, where the edbrowse temp directory is.
Unix is of course a different philosophy:  ~/.ebcache
Hopefully I did that part right.
We'll let you know when we have something for you to test.


Karl Dahlke

  reply	other threads:[~2017-01-28  2:35 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
2017-01-27 19:59     ` Karl Dahlke
2017-01-28  2:06       ` Geoff McLane
2017-01-28  2:36         ` Karl Dahlke [this message]
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=20170027213623.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --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).