From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Two strange messages while building Emacs on MS-Windows Date: Sat, 08 Dec 2012 12:35:03 +0100 Message-ID: <87y5h8ydy0.fsf@wanadoo.es> References: <83mwxpmtp6.fsf@gnu.org> <83d2ylm0em.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1354966534 25340 80.91.229.3 (8 Dec 2012 11:35:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 8 Dec 2012 11:35:34 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 08 12:35:47 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ThIh6-0003lf-44 for ged-emacs-devel@m.gmane.org; Sat, 08 Dec 2012 12:35:44 +0100 Original-Received: from localhost ([::1]:40635 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThIgt-0004Ef-UD for ged-emacs-devel@m.gmane.org; Sat, 08 Dec 2012 06:35:31 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:33877) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThIgp-0004DN-Pd for emacs-devel@gnu.org; Sat, 08 Dec 2012 06:35:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ThIgn-0004Ip-E4 for emacs-devel@gnu.org; Sat, 08 Dec 2012 06:35:27 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:42191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThIgn-0004Ih-7Z for emacs-devel@gnu.org; Sat, 08 Dec 2012 06:35:25 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ThIgu-0003ZP-VJ for emacs-devel@gnu.org; Sat, 08 Dec 2012 12:35:32 +0100 Original-Received: from 126.red-88-13-105.dynamicip.rima-tde.net ([88.13.105.126]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 08 Dec 2012 12:35:32 +0100 Original-Received: from ofv by 126.red-88-13-105.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 08 Dec 2012 12:35:32 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 126.red-88-13-105.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:Q1JA2HfhOJ/GQQ8ThgPDBMxE62w= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155367 Archived-At: joakim@verona.se writes: >> Why don't you try? I don't think anyone did, or at least we didn't >> hear about that. > > Okay, I'll have a go. > > http://www.gnu.org/software/emacs/windows/Getting-Emacs.html > > seems to indicate one uses Mingw on windows to compile Emacs. > Is that correct? > > I am familiar with cross-compiling for windows on gnu/linux. Would that > work? For cross-compiling, there are a few difficult passages: * Mixed build mode: you build some pieces with native tools (the cross-compiler, etc) but other pieces, like the .elc files, shall be built with the products (temacs/emacs executable) on the target environment, which implies running some temacs/emacs under wine. Dumping should also be done under wine. * Most likely, the W32 makefiles are far from supporting cross-compiling. They also would need to work on the GNU/Linux-MSWindows mixed environment and my impression is that they strongly depend on MSWindows features all the way. * The "regular" configure&make used elsewhere could be adapted by setting the appropriate knobs at configure-time and make-time (setting variables like CC, EMACS, etc.) The problem I've seen so far is that the makefiles works on the native file system, while wine works on its own file system (with different root, volume letters and all). So commands executed under wine would take the wrong pathnames. Adapting that seems tricky. OTOH, a MS Windows Emacs install appears to work well enough under Wine. I managed to lock both Emacs and the KDE desktop (!) with a simple operation (had to switch to a text-mode console and kill wine from there) but it seems that it should work for byte compiling and, hopefully, dumping. This means that, starting from `wine cmd.exe', installing the *native* mingw compiler (not the cross-compiler) and building with the MS Windows procedure, maybe a full MS Windows build can be achieved. Not something that I would advise for an official release, though.