[PATCH 2 of 8] setup: compile zstd C extension

Gregory Szorc gregory.szorc at gmail.com
Fri Nov 11 04:23:34 EST 2016


# HG changeset patch
# User Gregory Szorc <gregory.szorc at gmail.com>
# Date 1478845595 28800
#      Thu Nov 10 22:26:35 2016 -0800
# Node ID 32c2b8ca42a574f83426eaa19c89a8ff51c0e6de
# Parent  55a915a256129ce6f8b6e496e0829efce86775af
setup: compile zstd C extension

Now that zstd and python-zstandard are vendored, we can start compiling
them as part of the install.

python-zstandard provides a self-contained Python function that returns
a distutils.extension.Extension, so it is really easy to add zstd
to our setup.py without having to worry about defining source files,
include paths, etc. The function even allows specifying the module
name the extension should be compiled as. This conveniently allows us
to compile the module into the "mercurial" package so "our" version
won't collide with a version installed under the canonical "zstd"
module name.

diff --git a/setup.py b/setup.py
--- a/setup.py
+++ b/setup.py
@@ -581,6 +581,10 @@ extmodules = [
               ['hgext/fsmonitor/pywatchman/bser.c']),
     ]
 
+sys.path.insert(0, 'contrib/python-zstandard')
+import setup_zstd
+extmodules.append(setup_zstd.get_c_extension('mercurial.zstd'))
+
 try:
     from distutils import cygwinccompiler
 


More information about the Mercurial-devel mailing list