Lines Matching +full:- +full:dpybind11_findpython

41 .. code-block:: cpp
52 provided by the caller -- in fact, it does nothing at all.
54 .. code-block:: python
59 pybind11 is also affected by such language-level conventions, which means that
70 .. code-block:: cpp
76 .. code-block:: cpp
89 .. code-block:: cpp
103 .. code-block:: cpp
111 .. code-block:: cpp
114         m.def("sub", [](int a, int b) { return a - b; });
119 .. code-block:: pycon
144 specifying a larger value, e.g. ``-ftemplate-depth=1024`` on GCC/Clang. The
150 "‘SomeClass’ declared with greater visibility than the type of its field ‘SomeClass::member’ [-Watt…
154 ``-fvisibility`` flag.  pybind11 code internally forces hidden visibility on
155 all internal code, but if non-hidden (and thus *exported*) code attempts to
159 To avoid it, make sure you are specifying ``-fvisibility=hidden`` when
162 As to why ``-fvisibility=hidden`` is necessary, because pybind modules could
165 potentially-incompatible symbols defined in another.  While Python extension
170 ``-fvisibility=hidden``.
172 Additionally, ``-fvisiblity=hidden`` can deliver considerably binary size
192     .. code-block:: none
198     .. code-block:: cpp
204 .. code-block:: cpp
210 hand, it's silly to even give this function a name -- after all, it's just a
215 This can be achieved by specifying the parameter ``-fvisibility=hidden`` to GCC
221 In addition to decreasing binary size, ``-fvisibility=hidden`` also avoids
234 Common gotchas to watch out for involve not ``free()``-ing memory region
235 that that were ``malloc()``-ed in another shared library, using data
239 How can I properly handle Ctrl-C in long-running functions?
242 Ctrl-C is received by the Python interpreter, and holds it until the GIL
243 is released, so a long-running function won't be interrupted.
252 .. code-block:: cpp
269 The CMake-based build system will try to automatically detect the installed
272 ``CMakeCache.txt`` and then add ``-DPYTHON_EXECUTABLE=$(which python)`` to your
276 You can alternatively try ``-DPYBIND11_FINDPYTHON=ON``, which will activate the
295 .. code-block:: cmake
305 .. code-block:: cmake
325    However, you will have to use the target-based system, and do more setup
328    into an existing system, like scikit-build's Python helpers.
336 .. code-block:: bash
342        title = {pybind11 -- Seamless operability between C++11 and Python}