edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] quick js
Date: Sun, 07 Mar 2021 11:37:25 -0800	[thread overview]
Message-ID: <875z22iwlm.fsf@the-brannons.com> (raw)
In-Reply-To: <20210207142717.eklhad@comcast.net> (Karl Dahlke's message of "Sun, 07 Mar 2021 14:27:17 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> As per the big question of do we even support windows and/or cmake any
> more, I don't know.

Nowadays there is the Windows Subsystem for Linux (WSL), which is
essentially a Linux compatibility layer for Windows.
I'd be surprised if the static binaries didn't just run out of the box
under WSL.  So it's possible that the point is moot now, and we can
assume a *nix environment.

-- 
Chris Brannon
Founder: Blind and Low Vision Unix Users Group (https://blvuug.org/).
Personal website: (https://the-brannons.com/)
Chat: IRC: teiresias on freenode, XMPP: chris@chat.number89.net


  reply	other threads:[~2021-03-07 19:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 13:26 Karl Dahlke
2021-03-07 16:15 ` Chris Brannon
2021-03-07 16:44   ` Karl Dahlke
2021-03-07 17:15     ` Chris Brannon
2021-03-07 18:40       ` Geoff McLane
2021-03-07 19:27         ` Karl Dahlke
2021-03-07 19:37           ` Chris Brannon [this message]
2021-03-08  8:46             ` Karl Dahlke
2021-03-08 19:31               ` Geoff McLane
2021-03-08 21:18                 ` Karl Dahlke
2021-03-09 10:23               ` Kevin Carhart
2021-03-09 14:37                 ` Geoff McLane
2021-03-09 22:52                   ` Kevin Carhart
     [not found]                   ` <20210210053836.eklhad@comcast.net>
2021-03-14 20:36                     ` Geoff McLane
2021-03-15  9:44                       ` 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=875z22iwlm.fsf@the-brannons.com \
    --to=chris@the-brannons.com \
    --cc=edbrowse-dev@edbrowse.org \
    --subject='Re: [edbrowse-dev] quick js' \
    /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

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).