Great :)
-Øyvind 2014-11-03 16:26 GMT+01:00 Johan Hake <[email protected]>: > No it is not :) > > It is included using #include but not %include. > > I can push a fix for this. > > Johan > > On Mon, Nov 3, 2014 at 4:22 PM, Øyvind Evju <[email protected]> wrote: > >> Yes, it is. >> >> >> -Øyvind >> >> 2014-11-03 16:09 GMT+01:00 Johan Hake <[email protected]>: >> >>> Can you check >>> >>> if dolfin/swig/common/pre.i >>> >>> is included in the generated >>> >>> .instant/cache/dolfin_compile_code_XXX/dolfin_compile_code_XXX.i >>> >>> file? In that file we include tghe petsc4py.i with all the relevant >>> typesmaps. So if we do not include that file we probably should :) >>> >>> Johan >>> >>> On Mon, Nov 3, 2014 at 3:52 PM, Øyvind Evju <[email protected]> wrote: >>> >>>> When petsc4py is installed, the mpi_comm_world-function returns a >>>> petsc4py.PETSc.Comm-object. I guess this is true for all MPI communicators. >>>> When writing an extension module using a MPI_Comm as argument, this fails. >>>> >>>> MWE: >>>> >>>> >>>> >>>> >>>> >>>> >>>> *from dolfin import *cpp_module="""void foo(MPI_Comm comm) >>>> {}"""compiled_module = >>>> compile_extension_module(cpp_module)compiled_module.foo(mpi_comm_world())* >>>> >>>> I guess this is related to this: >>>> https://bitbucket.org/fenics-project/dolfin/issue/195/petsc4py-applies-own-typemap-for-mpi_comm >>>> >>>> Any way to work with this? >>>> >>>> >>>> -Øyvind >>>> >>>> >>>> _______________________________________________ >>>> fenics mailing list >>>> [email protected] >>>> http://fenicsproject.org/mailman/listinfo/fenics >>>> >>>> >>> >> >
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
