[SciPy-dev] Re: build_flib.py again

Pearu Peterson pearu at scipy.org
Wed Oct 29 03:37:09 CST 2003



On Wed, 29 Oct 2003, [iso-8859-15] Berthold Höllmann wrote:

> > The rationale is that all supported compilers should behave in 
> > the same way, that is, lower cases and append underscore to fortran 
> > symbols. Different compilers may behave differently in this respect and
> > with additional switches one can "tune" a compiler as needed.
> > Earlier compaq_visual_fortran_compiler did not follow this
> > convention and hence the changes. Sorry that it broke some of your 
> > codes and I hope it is not too much trouble for you to fix them.
> 
> But do you do with Third party delivered libraries you want to
> wrap. We have a set of huge libraries where we can't compile of our
> own. From time to time we need/have fortran wrapper around these
> libraries that then need to be wrapped for python. These Fortran
> wrapper are only needed for the Python wrapper and as such are
> compiled as library unsing distutils. Would it be possible to provide
> a mechanism to allow user defined settings for the "switches" to make
> the libraries work?

Could you give a more detailed example of the fortran wrapper and how do 
you wrap it to Python? If these wrappers can be modified e.g. by inserting 
f2py directives, then `fortranname` .pyf file command might be what you 
need.

Pearu





More information about the Scipy-dev mailing list