unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David R <angel_ov_north@tiscali.co.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: compiling emacs using cygwin
Date: Sun, 27 May 2007 12:47:41 +0100	[thread overview]
Message-ID: <46596fd9_4@mk-nntp-2.news.uk.tiscali.com> (raw)
In-Reply-To: <mailman.1306.1180211913.32220.help-gnu-emacs@gnu.org>

Eric Hanchrow wrote:
> I've found building Emacs on Windows to be difficult, although I've
> written down what works on
> http://www.emacswiki.org/cgi-bin/wiki/BuildingOnWindowsTableofContents.
> 
> You seem to be trying to build a "native Windows" binary, as opposed
> to a Cygwin binary.  Is that right?
I am not quite sure. I was attempting to use cygwin to compile it and I 
presumed that this will produce a native windows binary.
I have used MingW will reasonable success.  It produces an emacs from 
the nt version which runs on win XP but its appearance looks a bit 
shoddy, as thought it only uses 16 colours.  I presume that this is 
because I did not included any image support stuff like the link you 
mentioned does suggest.

> If you want to build a Cygwin binary, install gcc 4 from source (yes,
> that's a pain, but it works "out of the box") and then build Emacs
> with the usual Unix-style "./configure; make" (i.e., use ./configure
> instead of nt/configure.bat).

This is a bit of a problem to install gcc4 from source because the setup 
utility only goes up to version 3.4.4
I have a few questions
      1.  How do I discover the version of my gcc without going to the 
setup utility?
      2.  Is there anywhere on the net which gives me a "hold your hand" 
guide to compiling gcc from source on cygwin.  I have found for linux 
but not unixy shells.
      3.  I have looked for a good introduction to unix via cygwin but 
have not found any useful stuff for the beginner.  Any suggestions?

Thanks
David R

  parent reply	other threads:[~2007-05-27 11:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 16:15 compiling emacs using cygwin David R
2007-05-26 20:35 ` Eric Hanchrow
2007-05-27  3:13 ` Eli Zaretskii
     [not found] ` <mailman.1306.1180211913.32220.help-gnu-emacs@gnu.org>
2007-05-27 11:47   ` David R [this message]
2007-05-27 13:23     ` Eric Hanchrow
2007-05-27 19:52     ` Eli Zaretskii
     [not found]     ` <mailman.1330.1180273121.32220.help-gnu-emacs@gnu.org>
2007-05-29 10:49       ` David R
2007-05-29 20:29         ` Eric Hanchrow
     [not found]         ` <mailman.1406.1180471209.32220.help-gnu-emacs@gnu.org>
2007-06-15 14:38           ` David R
2007-06-15 17:56             ` Eric Hanchrow
     [not found]             ` <mailman.2204.1181931525.32220.help-gnu-emacs@gnu.org>
2007-06-17 17:48               ` David R
     [not found]     ` <mailman.1336.1180295540.32220.help-gnu-emacs@gnu.org>
2007-05-29 10:52       ` David R
2007-05-29 19:34         ` Eli Zaretskii
     [not found]         ` <mailman.1400.1180467287.32220.help-gnu-emacs@gnu.org>
2007-06-15 22:08           ` David R
2007-06-16 10:50             ` Eli Zaretskii
2007-06-02  3:53 ` Kevin Rodgers
     [not found] ` <mailman.1488.1180756520.32220.help-gnu-emacs@gnu.org>
2007-06-17 23:41   ` David R

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=46596fd9_4@mk-nntp-2.news.uk.tiscali.com \
    --to=angel_ov_north@tiscali.co.uk \
    --cc=help-gnu-emacs@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.
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).