XDress is an automatic wrapper generator for C/C++ written in pure Python. Currently, xdress may generate Python bindings (via Cython) for C++ classes & functions and in-memory wrappers for C++ standard library containers (sets, vectors, maps). In the future, other tools and bindings will be supported.
The main enabling feature of xdress is a dynamic type system that was designed with the purpose of API generation in mind.
Go here for the latest version of the docs!
:ref:`Go here for previous versions of the code & documentation. <previous_versions>`
.. toctree::
:maxdepth: 1
tutorial
advtut
libref/index
rcdocs
previous/index
other/index
faq
authors
Since xdress is pure Python code, the pip or easy_install may be used
to grab and install the code:
$ pip install xdress $ easy_install xdress
The source code repository for xdress may be found at the GitHub project site. You may simply clone the development branch using git:
git clone git://github.com/xdress/xdress.git
Also, if you wish to have the optional BASH completion, please add the
following lines to your ~/.bashrc file:
# Enable completion for xdress eval "$(register-python-argcomplete xdress)"
XDress currently has the following external dependencies,
Run Time:
- pycparser, optional for C
- GCC-XML, optional for C++
- dOxygen, optional for docstrings
- lxml, optional (but nice!)
- argcomplete, optional for BASH completion
Compile Time:
Test Time:
To see examples of xdress in action (and sample run control files), here are a few places to look:
- xdress/tests/cproj: This is a fully functioning sample C project which uses xdress locally.
- xdress/tests/cppproj: This is a fully functioning sample C++ project which uses xdress locally.
- PyNE: This uses xdress to generate STL container wrappers.
- Bright: This uses xdress to automatically wrap a suite of interacting C++ class. This was the motivating use case for the xdress project.
XDress has two major test types: unit tests which test library functionality and integration tests which test the command line tool, the parsers, compilers, etc. The unit tests are generally fast while the integration are slower. From the tests/ directory you may use nose to run the tests together or individually:
# Go into the tests dir $ cd tests # Run just the unit tests tests $ nosetests -a unit # Run just the integration tests tests $ nosetests -a integration # Run all of the tests together tests $ nosetests
Note that the integration tests require CMake in order to build the sample projects.
If you have questions or comments, please send them to the mailing list [email protected] or contact the author directly or open an issue on GitHub.
We highly encourage contributions to xdress! If you would like to contribute, it is as easy as forking the repository on GitHub, making your changes, and issuing a pull request. If you have any questions about this process don't hesitate to ask the mailing list ([email protected]).