This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

FFTW3, Shared Libraries, libtool


Hi all,

I am looking at packaging fftw3, a library for fast fourier transforms, for use
with octave.  This is a nice gpl package that has been autoconfiscated, and
builds out-of-tree properly, making it work well with g-b-s.  octave can be
built to use fftw3 instead of its default routines to perform fft's.

I have run into a snag, though, because despite being configured to build
shared libraries, I see no shared libraries when the fftw3 build completes.

When the build is complete, there is a libfftw3.a and libfftw3.la file
installed in usr/lib, and information in libfftw3.la (an ascii file created by
libtool) indicates there was no dll built, only a static library (libfftw3.a).

The configuration process creates a shell script labeled libtool in the build
directory, which appears to be based on some older version of gnu libtool.  So,
I'm wondering where to go from here.  I'm not very familiar with libtool, and
wonder how it is that this shell script gets created without the cygwin libtool
package being installed.  Perhaps the cygwin version would work better, i.e.
actually create the dll?  However, reading the libtool script indicates it has
configuration information created during execution of the configuration script.
 I'm not sure how to tell configure to use an installed version of libtool
instead of the version that is shipped with the source.

Anyone have ideas on this?

Thanks,

Jim Phillips


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]