From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building Emacs-cvs on Cygwin (GCC summary)
Date: Sun, 05 Nov 2006 13:55:40 +0200 [thread overview]
Message-ID: <u1woi3y6b.fsf@gnu.org> (raw)
In-Reply-To: <87hcxemahr.fsf@w2kpicasso.cante.net> (message from Jari Aalto on 05 Nov 2006 12:52:16 +0200)
> From: Jari Aalto <jari.aalto@cante.net>
> Date: 05 Nov 2006 12:52:16 +0200
> >
> > etc/PROBLEMS seems more appropriate.
In the meantime, I already added to PROBLEMS an entry about Cygwin
build with GCC 3.4.4.
> Woudl it be possible to use OS specific file:
>
> etc/NOTES.Cygwin
It's possible, but why would we want to do that? There are at least
several good reasons not to:
. System-specific files are a pain from the user's perspective, since
the users need to be told where to find instructions relevant for
their platform, and there's no good place to put these instructions
(obviously, those instructions cannot be in a platform-specific
files). the etc/ directory is very large, so letting users look
for the files on their own will make things hard on them
. etc/PROBLEMS has an item in the Help menu, and searching it for
"Cygwin" is trivial. Many Emacs users already know about PROBLEMS
and will look there when faced with a problem.
. Cygwin build is, for all practical purposes, a Posix build, so
users will probably assume that general Unix issues hold for it as
well, and look for instructions and other build-related material in
the general files, not in some OS-specific ones.
next prev parent reply other threads:[~2006-11-05 11:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 1:22 Building Emacs-cvs on Cygwin (GCC summary) Maks Romih
2006-10-30 19:16 ` Richard Stallman
2006-10-30 20:31 ` Eric Hanchrow
2006-10-30 21:05 ` Eli Zaretskii
2006-10-30 21:26 ` Eric Hanchrow
2006-10-30 21:44 ` Jason Rumney
2006-11-05 10:52 ` Jari Aalto
2006-11-05 11:55 ` Eli Zaretskii [this message]
2006-10-30 21:06 ` Eli Zaretskii
2006-11-04 12:12 ` Eli Zaretskii
2006-11-21 1:28 ` 22.1 Cygwin emacs timeframe query Angelo Graziosi
2006-11-21 1:46 ` Angelo Graziosi
2006-11-21 9:35 ` Angelo Graziosi
2006-11-22 14:49 ` Failures in build Emacs-CVS on Cygwin Angelo Graziosi
2006-11-22 22:23 ` Eli Zaretskii
2006-11-23 0:07 ` Angelo Graziosi
2006-11-23 4:15 ` Eli Zaretskii
2006-11-23 14:04 ` Angelo Graziosi
2006-11-23 23:55 ` Angelo Graziosi
2006-11-24 21:17 ` Eli Zaretskii
2006-11-24 23:32 ` Angelo Graziosi
2006-11-25 11:07 ` Eli Zaretskii
2006-11-25 9:52 ` Angelo Graziosi
2006-11-25 11:06 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2006-10-28 12:16 Building Emacs-cvs " Eli Zaretskii
2006-10-29 11:13 ` Building Emacs-cvs on Cygwin (GCC summary) Angelo Graziosi
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u1woi3y6b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).