From: Eli Zaretskii <eliz@gnu.org>
To: Hannu Koivisto <azure@iki.fi>
Cc: emacs-devel@gnu.org
Subject: Re: A few Windows build fixes
Date: Mon, 29 Aug 2011 09:28:55 -0400 [thread overview]
Message-ID: <E1Qy1tX-00082G-6g@fencepost.gnu.org> (raw)
In-Reply-To: <83mxes4e84.fsf@kalahari.s2.org> (message from Hannu Koivisto on Mon, 29 Aug 2011 15:03:07 +0300)
> From: Hannu Koivisto <azure@iki.fi>
> Date: Mon, 29 Aug 2011 15:03:07 +0300
>
> > trouble. By contrast, GnuWin32 is a collection of native Windows
> > ports of GNU software. They don't "fix" any file names, and they
> > support native Windows file name format, either with forward slashes
> > or with backslashes.
>
> That sounds very good compared to msys. However, I have no need
> for such native tools so I'm not going to install them and test
> with them.
You are not required to test them yourself, sorry if I was unclear
about that. The only requirement is to not use anything that is
guaranteed to break the other environments. Any other issues that are
not immediately clear by just reading the diffs will be in due time
discovered by others, who do have those tools installed, and we can
deal with them at that time.
> The fact that you see one environment working fine and I see others
> failing is precisely the problem I'm talking about. The makefiles
> would be better off separated into environment specific parts and
> environment independent parts so that users of one environment
> could fix their environment specific parts or generic parts without
> worrying too much about breaking other environments (like I've just
> done with GnuWin32). Unfortunately this is nontrivial or at least
> ugly with plain make.
Hmm... this actually gives me an idea. How about providing a
completely separate set of Makefile.cygwin-in files, whose sole target
will be the native build with Cygwin tools? Then the only changes
that need to be aware of the other Windows builds will be in
nt/configure.bat.
Of course, the downside of this would be the need to maintain a
separate set of Makefiles, although we could factor out at least the
dependencies to make it less painful... Hmm... Alternatively, would
it be possible to have just a separate nt/cygwin.defs file, to be used
instead of gmake.defs, and fix any issues specific to Cygwin, like
/cygdrive etc., in that file?
> > The main toolchain that is currently supported for building the native
> > Windows port of Emacs is MinGW accompanied by a few GnuWin32 ports
> > (`cp', `rm', `mv'). So supporting MinGW which needs this,
> > is indeed more important than supporting the build with Cygwin, yes.
>
> I think you should consider replacing the current largely obsolete
> INSTALL file and mention only this one supported build environment.
You are probably right, I will add this to my TODO.
> >> Not solving this means that "make install" won't work when cmd is
> >> not used.
> >
> > It will work if INSTALL_DIR already exists.
>
> Actually it doesn't, because the makefiles try to create the same
> directory (at least $INSTALL_DIR/bin, possibly others) several
> times.
Actually, it does, because each mkdir command is invoked with the `-'
flag before it. ;-)
> I'm not going to work on these changes in the foreseeable future,
> though, so don't expect updated versions soon. In fact, if I'll
> work on building Emacs on Windows later, I think I'd rather use my
> time on trying to fix the Visual C++/nmake build, which was my
> primary choice anyway.
The MSVC build indeed needs some care, I think no one has tried to use
it for a long time. You will probably find the patch and the
discussions in these 2 threads useful:
http://lists.gnu.org/archive/html/emacs-devel/2010-12/msg00408.html
http://lists.gnu.org/archive/html/emacs-devel/2011-01/msg00108.html
I still have on my TODO to apply those patches after some changes, as
discussed on the list, but if you can do that as part of your work,
and also update the patch wrt the latest trunk while at that, it would
be much better, as I don't really use MSVC myself (and none of the
other contributors to the w32 port does, AFAIK).
Thanks.
next prev parent reply other threads:[~2011-08-29 13:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 22:46 A few Windows build fixes Hannu Koivisto
2011-08-29 6:15 ` Eli Zaretskii
2011-08-29 8:18 ` Hannu Koivisto
2011-08-29 10:05 ` Eli Zaretskii
2011-08-29 12:03 ` Hannu Koivisto
2011-08-29 13:28 ` Eli Zaretskii [this message]
2011-08-29 15:55 ` Stefan Monnier
2011-08-29 16:11 ` Eli Zaretskii
2011-08-29 15:48 ` Stefan Monnier
2011-08-29 16:08 ` Eli Zaretskii
2011-08-29 19:48 ` Jan Djärv
2011-08-31 2:42 ` Vijay Lakshminarayanan
2011-08-31 6:11 ` Eli Zaretskii
2011-08-31 13:17 ` Stefan Monnier
2011-09-01 17:55 ` Vijay Lakshminarayanan
2011-09-02 0:14 ` Andy Moreton
2011-09-02 7:07 ` Eli Zaretskii
2011-09-02 11:43 ` Andy Moreton
2011-09-02 12:48 ` Stefan Monnier
2011-09-02 14:14 ` Eli Zaretskii
2011-09-02 14:18 ` Jason Rumney
2011-09-02 14:47 ` Stefan Monnier
2011-09-02 14:05 ` Eli Zaretskii
2011-09-02 14:48 ` Stefan Monnier
2011-09-02 15:48 ` Vijay Lakshminarayanan
2011-09-02 16:47 ` Eli Zaretskii
2011-09-06 2:49 ` Stefan Monnier
2011-09-06 4:33 ` Eli Zaretskii
2011-09-06 18:04 ` Stefan Monnier
2011-09-06 18:26 ` Eli Zaretskii
2011-09-07 3:29 ` Stefan Monnier
2011-09-07 5:17 ` Eli Zaretskii
2011-09-07 12:50 ` Stefan Monnier
2011-09-07 16:48 ` Eli Zaretskii
2011-09-08 8:33 ` Hannu Koivisto
2011-09-08 8:49 ` Eli Zaretskii
2011-09-08 9:06 ` Hannu Koivisto
2011-09-02 15:50 ` Vijay Lakshminarayanan
2011-09-02 2:48 ` Stefan Monnier
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=E1Qy1tX-00082G-6g@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=azure@iki.fi \
--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 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.