itaps-parallel IMeshP_protos.h

txie at scorec.rpi.edu txie at scorec.rpi.edu
Fri Oct 24 12:34:22 CDT 2008


Hi, Jason,

Thanks for sharing these files. They are useful.

But I have one question about how to use them (see below). Thanks.


> Devine, Karen D wrote:
>> Thanks for your reply, Jason.  Since iMeshP.h includes iMeshP_protos.h,
>> we
>> should have iMeshP_protos.h in the repository; otherwise, builds that
>> include iMeshP.h will fail when they can't find iMeshP_protos.h.  If
>> iMeshP_protos.h is for fortran name mangling only, can we name the file
>> something like iMeshP_fortran_protos.h?   Also, I like your decision to
>> have
>> these definitions in a separate file (one for each interface), as users
>> don't really need to worry about them and having them in the main
>> interface
>> file would be distracting.
>
>
> I've attached all of our *_protos.h files.  However, these files in turn
> include another header that will be missing: MBCN_FCDefs.h.  We generate
> that header using autoconf such that it contains the appropriate
> definition
> of FC_FUNC_ for the configured Fortran compiler.
>
> - jason
>

I compared iMesh_protos.h before and the file you sent just now. I found
the following difference:


[piglet:include]:diff iMesh_protos.h /users/txie/tmp/iMesh_protos.h
1c1,2
< #define F77_FUNC_(name,NAME) name ## _
---
> #include "MBCN_FCDefs.h"
> #ifdef FC_FUNC_


One question: it seems that FMDB needs to create one header file similar
to MBCN_FCDefs.h using autotools to use these *_protos.h files, right? If
yes, may you let us know how to create it and how this file looks like?
Thanks.


Thanks,

Ting








More information about the itaps-parallel mailing list