Author: Armin Rigo <ar...@tunes.org>
Branch:
Changeset: r1616:f7fa2106ddf3
Date: 2014-12-31 19:34 +0100
http://bitbucket.org/cffi/cffi/changeset/f7fa2106ddf3/
Log: Document 'relative_to'.
diff --git a/doc/source/index.rst b/doc/source/index.rst
--- a/doc/source/index.rst
+++ b/doc/source/index.rst
@@ -673,7 +673,9 @@
whenever you change your sources.
.. versionadded:: 0.9
- You can give C++ source code in ``ffi.verify()``::
+ You can give C++ source code in ``ffi.verify()``:
+
+::
ext = ffi.verify(r'''
extern "C" {
@@ -685,6 +687,27 @@
The optional ``flags`` argument has been added, see ``man dlopen`` (ignored
on Windows). It defaults to ``ffi.RTLD_NOW``.
+.. versionadded:: 0.9
+ The optional ``relative_to`` argument is useful if you need to list
+ local files passed to the C compiler:
+
+::
+
+ ext = ffi.verify(..., sources=['foo.c'], relative_to=__file__)
+
+The line above is roughly the same as::
+
+ ext = ffi.verify(..., sources=['/path/to/this/file/foo.c'])
+
+except that the default name of the produced library is built from the
+CRC checkum of the argument ``sources``, as well as most other arguments
+you give to ``ffi.verify()`` -- but not ``relative_to``. So if you used
+the second line, it would stop finding the already-compiled library
+after your project is installed, because the ``'/path/to/this/file'``
+suddenly changed. The first line does not have this problem.
+
+---------------------
+
This function returns a "library" object that gets closed when it goes
out of scope. Make sure you keep the library object around as long as
needed.
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
https://mail.python.org/mailman/listinfo/pypy-commit
