Pierre GM wrote:
> On Tuesday 20 March 2007 18:13:09 Robert Kern wrote:
>> Pierre GM wrote:
>> Hmm. Okay, put the FORTRAN files into a library instead.
>
> Robert, Pearu, great ! Creating a library did the trick. I eventually come
> with that:
>
> def configuration(parent
On Tuesday 20 March 2007 18:13:09 Robert Kern wrote:
> Pierre GM wrote:
> Hmm. Okay, put the FORTRAN files into a library instead.
Robert, Pearu, great ! Creating a library did the trick. I eventually come
with that:
def configuration(parent_package='',top_path=None):
Pierre GM wrote:
> On Tuesday 20 March 2007 17:46:28 Robert Kern wrote:
>
>> The first file in the sources list should be the one that actually
>> implements the module, i.e. the C file generated by Pyrex. FORTRAN files
>> specified after the first one won't be processed by f2py.
>
> Mmh. I had t
> On Tuesday 20 March 2007 17:46:28 Robert Kern wrote:
>
>> The first file in the sources list should be the one that actually
>> implements the module, i.e. the C file generated by Pyrex. FORTRAN files
>> specified after the first one won't be processed by f2py.
>
> Mmh. I had to get rid of the '*
On Tuesday 20 March 2007 17:46:28 Robert Kern wrote:
> The first file in the sources list should be the one that actually
> implements the module, i.e. the C file generated by Pyrex. FORTRAN files
> specified after the first one won't be processed by f2py.
Mmh. I had to get rid of the '*.pyx' and
Pierre GM wrote:
> All,
> I'm trying to write a numpy.distutils setup.py for a pyrex module that
> involves both external C and fortran sources, and where the fortran sources
> need to be linked w/ blas and lapack. Here's what I have so far:
>
> ##
> def configura
All,
I'm trying to write a numpy.distutils setup.py for a pyrex module that
involves both external C and fortran sources, and where the fortran sources
need to be linked w/ blas and lapack. Here's what I have so far:
##
def configuration(parent_package='',top_path
