all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: W32 version crashes on C-g
Date: Sat, 18 Mar 2006 13:45:50 +0100	[thread overview]
Message-ID: <f7ccd24b0603180445g6eefd3a1ubead963149d8e480@mail.gmail.com> (raw)
In-Reply-To: <uirqcvv1t.fsf@gnu.org>

On 3/18/06, Eli Zaretskii <eliz@gnu.org> wrote:

> Please feel free to suggest such refinements.

You only have to take a look at Lennart's EmacsW32 pages to see which
kinds of things aren't easy for beginners, and are not described in
nt/INSTALL.

> It's supposed to be, and I think it comes close.

As you say, it is a step-by-step guide to building Emacs, but not to
set up a working environment, and that's what causes trouble. Of
course once you've got every needed tool, building Emacs is easy.

> I disagree.  When I first built Emacs on Windows, I didn't need
> anything except setting up a working development environment.

I repeat: setting up the environment is the hardest part. Even if the
user is a developer, if he happens to have tools from GnuWin32, Cygwin
and MinGW in his PATH (it's happened to me a couple times), you can
get mysterious errors while running make, for example.

> (The only issue was
> the 3rd party image libraries that had incompatible headers.
> But that's hardly a problem with Emacs.)

But I'm not talking about "problems with Emacs", just problems for a
user to download the source tarball and turn it into a working Emacs
binary. Incompatible headers, or libraries (the image libraries have
quite a few dependencies) can be daunting for the inexperienced.

Or, to put it in another way: Kim can hardly be considered a newbie,
and it's clear that he could have set up a working environment and
compiled Emacs, given a little time. But he hadn't the time, he looked
at nt/INSTALL and did not find what he needed. Whether that's a
problem in contents or presentation, I don't know.

> I didn't need any bravery.

You're more resourceful that I am :-)

> I find it very simple, perhaps because the first thing I do is
> download GCC, Binutils, and every other ported GNU package (Coreutils,
> Sed, Grep, Gawk, Make, Texinfo, Diffutils, and Patch) one needs for
> decent development.

Perhaps. I've been developing on Windows for years and didn't need
most of that, until I started hacking Emacs; so your definition of
"decent development" and mine are dissimilar.

--
                    /L/e/k/t/u

  reply	other threads:[~2006-03-18 12:45 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 10:41 W32 version crashes on C-g Kim F. Storm
2006-03-17 11:46 ` Eric Lilja
2006-03-17 12:07 ` Eli Zaretskii
2006-03-17 12:28   ` Kim F. Storm
2006-03-17 12:32 ` Juanma Barranquero
2006-03-17 14:04   ` Kim F. Storm
2006-03-17 14:20     ` Juanma Barranquero
2006-03-17 14:49       ` Kim F. Storm
2006-03-17 16:07         ` Jason Rumney
2006-03-17 16:08         ` Lennart Borgman
2006-03-18  1:13           ` Kim F. Storm
2006-03-18  7:51             ` Lennart Borgman
2006-03-18 11:29             ` Eli Zaretskii
2006-03-17 16:52         ` Juanma Barranquero
2006-03-17 17:06           ` Drew Adams
2006-03-17 18:00           ` Lennart Borgman
2006-03-17 23:27             ` Juanma Barranquero
2006-03-18  0:01               ` Lennart Borgman
2006-03-18  5:49                 ` Juanma Barranquero
2006-03-18  7:48                   ` Lennart Borgman
2006-03-18 12:46                     ` Juanma Barranquero
2006-03-17 18:30           ` Binaries for W32 (was: W32 version crashes on C-g) Reiner Steib
2006-03-17 18:42             ` Drew Adams
2006-03-17 18:56               ` Lennart Borgman
2006-03-17 18:58                 ` Drew Adams
2006-03-20 18:32                   ` Drew Adams
2006-03-21 10:29                     ` Juanma Barranquero
2006-03-22 15:16                       ` Mathias Dahl
2006-03-25 10:15                       ` Eli Zaretskii
2006-03-18  1:21           ` W32 version crashes on C-g Kim F. Storm
2006-03-18  6:00             ` Juanma Barranquero
2006-03-18 11:42               ` Eli Zaretskii
2006-03-18 12:45                 ` Juanma Barranquero [this message]
2006-03-18 15:42                   ` Eli Zaretskii
2006-03-18 16:55                     ` Juanma Barranquero
2006-03-18 17:59                       ` Eli Zaretskii
2006-03-18 20:38                         ` Lennart Borgman
2006-03-18 21:42                           ` Juanma Barranquero
2006-03-18 20:46                   ` Lennart Borgman
2006-03-19  1:32               ` Kim F. Storm
2006-03-21 10:35                 ` Juanma Barranquero
2006-03-21 12:43                   ` Kim F. Storm
2006-03-21 15:22                     ` Juanma Barranquero
2006-03-18 10:52         ` Eli Zaretskii
2006-03-19  1:44           ` Kim F. Storm
2006-03-18 16:23         ` Eli Zaretskii
2006-03-18 17:14           ` Eric Hanchrow
2006-03-18 17:15           ` Chong Yidong
2006-03-18 18:10             ` Eli Zaretskii
2006-03-18 18:59             ` Jason Rumney
2006-03-18 19:11               ` Chong Yidong
2006-03-18 22:38                 ` Eli Zaretskii
2006-03-19  0:46           ` Kim F. Storm
2006-03-18 16:27         ` Eric Hanchrow
2006-03-18 17:56           ` Eli Zaretskii
2006-03-18 16:29         ` Eric Hanchrow
2006-03-18 18:19           ` Eli Zaretskii
2006-03-18 19:04           ` Jason Rumney
2006-03-18 10:40     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2006-03-17 12:58 LENNART BORGMAN

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=f7ccd24b0603180445g6eefd3a1ubead963149d8e480@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.