Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Compiling Gnus under MS Windows
Date: Tue, 18 Sep 2001 23:02:03 -0400	[thread overview]
Message-ID: <2nn13rrihg.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <66agu346.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Tue, 18 Sep 2001 13:53:29 +0200")

Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:

> Frank Schmitt <Azzrael@rz-online.de> writes:
>
>>When trying to do make under cygwin (configure works like a charm) I get
>>the following output:
> [well, it's broken]
> >What does this mean?
>>
>>Afterwards I tried to use the make.bat but this one only works with GNU
>>Emacs, not with XEmacs. I changed it so it would search for xemacs.exe
>>if it can't find emacs.exe and it seems that it worked, (at least I'm
>>now writing in my brandnew snapshot oort gnus) but I don't really know
>>if really everything is ok now.
>>
>>Well in fact what I wanted to say was: There's now obvious way to
>>compile Gnus under Window and XEmacs, this must be changed.
>
> Does this really not interest the maintainers of Gnus? 

It is interesting, but I don't play M$ Windows much.

> At least it should be possible to update the make.bat, so it works
> with XEmacs, too.

I've added make-x.bat into the Gnus CVS.

> I would be willing to do this if one would tell me which instruction
> have to be carried out and in which places the compilation under
> XEmacs differs from compilation under Gnu Emacs.

Another solution is to run nmake xemacs.mak.

Yet another solution is to manually change backslash to forward slash
in Makefile.

Hope these help.

ShengHuo


  reply	other threads:[~2001-09-19  3:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 12:55 Frank Schmitt
2001-09-07  6:54 ` ShengHuo ZHU
2001-09-07 13:34   ` Frank Schmitt
2001-09-18 11:53 ` Frank Schmitt
2001-09-19  3:02   ` ShengHuo ZHU [this message]
2001-09-19 10:36 ` David Maslen
2001-09-19 11:09   ` Frank Schmitt

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=2nn13rrihg.fsf@piglet.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).