:orphan:

|rss_image|  **pybind11 - 1/1** :ref:`Blog <ap-main-0>` :ref:`C++ (3) <ap-cat-C++-0>`

.. |rss_image| image:: feed-icon-16x16.png
    :target: ../_downloads/rss.xml
    :alt: RSS

----


.. index:: pybind11


.. _ap-cat-pybind11-0:

pybind11 - 1/1
++++++++++++++

.. blogpostagg::
    :title: Mixing pybind11 modules
    :date: 2019-03-19
    :keywords: pybind11,C++
    :categories: pybind11
    :rawfile: 2019/2019-03-19_splitcppmodule.rst

    My scenario was the following: expose a C++ class in
    one C++ module exported with :epkg:`pybind11`, then
    create a function in a another C++ module returning
    a result of this class. The solution for that is
    described in the following issue
    `Return type that is implemented in another library with another set of python bindings
    <https://github.com/pybind/pybind11/issues/616>`_, which
    links to this part of the documentation
    `Custom type casters <https://pybind11.readthedocs.io/en/stable/advanced/cast/custom.html>`_.
    and implemented in this module somewhere in
    `cbenchmark_dot.cpp <https://github.com/sdpython/cpyquickhelper/blob/master/cpyquickhelper/numbers/cbenchmark_dot.cpp#L608>`_.





----

|rss_image|  **pybind11 - 1/1** :ref:`2018-08 (2) <ap-month-2018-08-0>` :ref:`2019-02 (1) <ap-month-2019-02-0>` :ref:`2019-03 (1) <ap-month-2019-03-0>` :ref:`2019-09 (1) <ap-month-2019-09-0>` :ref:`2021-01 (1) <ap-month-2021-01-0>`