edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] statically linked edbrowse executable for Linux is finally here!
Date: Tue, 10 Jun 2014 06:34:00 -0700	[thread overview]
Message-ID: <87ppigdh2v.fsf@mushroom.PK5001Z> (raw)

Remember the good old days, when edbrowse was a single Perl script?
You could download it, plop it in a directory in $PATH, and go.  No
fuss, no muss.
Until late 2001 or so, that Perl script didn't even have any external
dependencies, aside from a working Perl.
It was one easily-deployed executable.
That's why I still occasionally use the Perl version of edbrowse.

Those days are back, at least if you're on Linux!
Here's a statically linked edbrowse executable:
http://the-brannons.com/edbrowse-static-linux
This was built from a snapshot taken in April, so it's not quite in sync
with git.  I'll fix that later.  Also, I'll eventually distribute a gpg
signature, so you can be assured that the binary actually came from me.

Unfortunately, it's around 9 megabytes in size, compared to a 223k Perl
script.
Plus, the Perl version remains useful for non-Linux hosts.
Anyway, this should make life easier for people who just want to get up
and running with edbrowse while avoiding the chore of building it for themselves.

I built this on Alpine Linux, and it is linked against musl, a new
implementation of the standard C library.  Cudos to Rich Felker for
releasing a full-featured libc that does *not* break static linking!
For people who like to read source, the musl codebase is also quite
readable.

-- Chris

                 reply	other threads:[~2014-06-10 13:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87ppigdh2v.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --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).