|Number of watchers on Github||236|
|Number of open issues||12|
|Average time to close an issue||3 months|
|Average time to merge a PR||about 14 hours|
|Open pull requests||2+|
|Closed pull requests||6+|
|Last commit||about 1 year ago|
|Repo Created||about 7 years ago|
|Repo Last Updated||5 months ago|
|Organization / Author||caldwell|
|Do you use build-emacs? Leave a review!|
|View open issues (12)|
|View build-emacs activity|
|View on github|
|Latest Open Source Launches|
Trendy new open source projects in your inbox! View examples
These are the emacs build scripts that produces the builds at http://emacsformacosx.com/.
The scripts are modular and are designed to be run on multiple build machines (or VMs) and integrate with continuous integration servers (the builds on emacsformacosx.com run from Jenkins now). This means that you can build whatever architectures you have access to.
Note that cross-compiling Emacs is (still) not possible due to the
step, which requires the binary that was built to be run. So if you want to
build an old architecture (like PowerPC), you need to be running on a system
that can actually execute binaries of that architecture.
Recent Emacs pretests are being distributed in
.tar.xz format. The
fetch-emacs-from-ftp script will convert from
.tar.bz2 so that
XZ doesn't need to be installed on every build machine. But you will need
xz program on the machines that runs
easiest way to get it is through homebrew:
brew install xz
There are 3 scripts that are designed to be run from some sort of Continuous
Integration software (the builds on http://emacsformacosx.com run from
Jenkins). All three scripts know the
--verbose command, and are nice and
loud when it is given.
This takes an ftp url (
ftp://ftp.gnu.org/gnu/emacs/, for example), and
downloads the latest version of the Emacs source code found there. It will
also convert the source from a
.tar.xz to a
.tar.bz2 (so that the main
build VMs don't need to have
This is the main build script. It takes a tar file and a
release) as input and unpacks the tar, builds it for a
single architecture, and tars up the resulting Emacs.app file.
You can tell it to build an architecture other than the default with the
--arch option (
Builds of the main Emacs source repository are expected to be packaged up into tars elsewhere. http://emacsformacosx.com has a Jenkins job that pulls down the latest code and then tars it up like so:
DATE=$(date "+%Y-%m-%d_%H-%M-%S") SHORT=$(git rev-parse --short HEAD) DIR=emacs-$DATE-$SHORT git archive --prefix="$DIR/" HEAD | tar x (cd $DIR && ./autogen.sh) tar cjf $DIR.tar.bz2 $DIR
This takes multiple tar files as input, unpacks and combines them into a
fat Emacs.app, then creates a final disk image (
.dmg). It takes an
--sign parameter (
--sign="my identity") which makes it code
sign the Emacs.app.
$ ./fetch-emacs-from-ftp -v ftp://ftp.gnu.org/pub/gnu/emacs + curl --continue-at - --silent -O ftp://ftp.gnu.org/pub/gnu/emacs/emacs-25.1.tar.xz shell(#<Th:0x007febed8a48b0>): /usr/local//brew//bin/xzcat emacs-25.1.tar.xz shell(#<Th:0x007febed8a48b0>): /usr/bin/bzip2 $ ls *.bz2 emacs-25.1.tar.bz2 $ ./build-emacs-from-tar -v -j 8 emacs-25.1.tar.bz2 release ... Lots out output snipped ... Built Emacs-25.1-10.12-x86_64.tar.bz2, Emacs-25.1-10.12-x86_64-extra-source.tar $ ./combine-and-package -v Emacs-25.1-10.12-x86_64.tar.bz2 ... More output snipped ... created: Emacs-25.1-universal.dmg
Copyright 2004-2016 David Caldwell firstname.lastname@example.org
The scripts and programs contained in this distribution are licensed under the GNU General Public License (v3.0). See the LICENSE file for details.