3.2. setup

3.2.1. Module Contents

3.2.1.1. Classes

CMakeExtension	Extension that uses '.c' files in place of '.pyx' files
CMakeBuild	Abstract base class for defining command classes, the "worker bees"

3.2.1.2. Functions

warning(s)

3.2.1.3. Attributes

color_warning
version
package_data

setup.color_warning

setup.warning(s)

setup.version

class setup.CMakeExtension(name, sourcedir='')

Bases: setuptools.Extension

Extension that uses ‘.c’ files in place of ‘.pyx’ files

class setup.CMakeBuild(dist)

Bases: setuptools.command.build_ext.build_ext

Abstract base class for defining command classes, the “worker bees” of the Distutils. A useful analogy for command classes is to think of them as subroutines with local variables called “options”. The options are “declared” in ‘initialize_options()’ and “defined” (given their final values, aka “finalized”) in ‘finalize_options()’, both of which must be defined by every command class. The distinction between the two is necessary because option values might come from the outside world (command line, config file, …), and any options dependent on other options must be computed after these outside influences have been processed – hence ‘finalize_options()’. The “body” of the subroutine, where it does all its work based on the values of its options, is the ‘run()’ method, which must also be implemented by every command class.

run()

Build extensions in build directory, then copy if –inplace

build_extension(ext)

setup.package_data