unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: windows build help
Date: Sat, 14 Oct 2017 10:15:41 -0500	[thread overview]
Message-ID: <86wp3xbw0y.fsf@stephe-leake.org> (raw)
In-Reply-To: <87376m9edg.fsf@russet.org.uk> (Phillip Lord's message of "Sat, 14 Oct 2017 12:07:39 +0100")

phillip.lord@russet.org.uk (Phillip Lord) writes:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>
>> phillip.lord@russet.org.uk (Phillip Lord) writes:
>>
>>> Another solution would be to run both builds in parallel; this fails,
>>> unfortunately, because the "out-of-source" build is not entirely out of
>>> source -- the .elc files are created in-source. If I launch both a 64
>>> and 32 bit build at the same time, they fight for whole compiles what,
>>> until one or both crash.
>>
>> Have two source checkouts. then you could also build in-source, although
>> I doubt that makes much difference.
>
> I thought about that, but the reason against it is that it takes much
> longer, because I have to build the elc twice.

Hmm. You are implying that the elc built for 32 bit emacs are identical
to the elc built for 64 bit emacs. 

Is that true? I would have guessed that most objects are either
32 bit or 64 bit; elisp manual 3.1 says the integer range depends on the
machine, and pointers should also.

If they are the same, then you should be able to write a script that
does:

1) parallel make to build elc using 32 bit
2) parallel make to build everything else, both 32 bit and 64 bit.

-- 
-- Stephe



  reply	other threads:[~2017-10-14 15:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84o9pyim1a.fsf@AigleRoyal>
     [not found] ` <v9tvzoyonq.fsf@fencepost.gnu.org>
     [not found]   ` <c26025cd-ccaa-70e1-94d4-003b7632bd19@gmail.com>
     [not found]     ` <bypoab3jsz.fsf@fencepost.gnu.org>
     [not found]       ` <vz1shf7dl4u.fsf@gmail.com>
     [not found]         ` <83r2up976t.fsf@gnu.org>
     [not found]           ` <CAM-tV-8BAheHD+gDjJ1N+jPYqg8a4MLKK7NEQH=KBWkwjGujuQ@mail.gmail.com>
     [not found]             ` <83bmlblfca.fsf@gnu.org>
     [not found]               ` <vz14lr373si.fsf@gmail.com>
2017-10-13 18:52                 ` windows build help Phillip Lord
2017-10-13 19:36                   ` Óscar Fuentes
2017-10-13 19:38                   ` Stephen Leake
2017-10-14 11:07                     ` Phillip Lord
2017-10-14 15:15                       ` Stephen Leake [this message]
2017-10-14 15:26                         ` Phillip Lord
2017-10-14 15:31                         ` Eli Zaretskii
2017-10-14 23:04                         ` Paul Eggert
2017-10-16  1:53                           ` Richard Stallman
2017-10-16  6:49                             ` Paul Eggert
2017-10-16 13:54                               ` Stefan Monnier
2017-10-13 19:47                   ` Noam Postavsky
2017-10-14 11:09                     ` Phillip Lord
2017-10-14  8:16 Angelo Graziosi
2017-10-14 11:16 ` Phillip Lord

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=86wp3xbw0y.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.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).