GNU Info

(python2.1-dist.info)Extension source files

---

Next: Preprocessor options Prev: Extension names and packages Up: Describing extension modules

---

Enter node , (file) or (file)node

Extension source files
----------------------

The second argument to the `Extension' constructor is a list of source
files.  Since the Distutils currently only support C/C++ extensions,
these are normally C/C++ source files.  (Be sure to use appropriate
extensions to distinguish C++ source files: `.cc' and `.cpp' seem to be
recognized by both UNIX and Windows compilers.)

However, you can also include SWIG interface (`.i') files in the list;
the `build_ext' command knows how to deal with SWIG extensions: it will
run SWIG on the interface file and compile the resulting C/C++ file
into your extension.

*SWIG support is rough around the edges and largely untested;
especially SWIG support of C++ extensions!  Explain in more detail here
when the interface firms up.*

On some platforms, you can include non-source files that are processed
by the compiler and included in your extension.  Currently, this just
means Windows message text (`.mc') files and resource definition
(`.rc') files for Visual C++. These will be compiled to binary resource
(`.res') files and linked into the executable.