[osgeo4w-dev] [osgeo4w] #397: FFTW misses import library
OSGeo4W
trac_osgeo4w at osgeo.org
Tue Nov 19 05:40:04 PST 2013
#397: FFTW misses import library
------------------------+---------------------------------------------------
Reporter: jmalik | Owner: osgeo4w-dev@…
Type: enhancement | Status: new
Priority: major | Component: Package
Version: | Keywords: fftw
------------------------+---------------------------------------------------
Comment(by jmalik):
Jef,
Before going any further : chances are that the 32bit package has been
generated from the prebuilt binaries distributed by the FFTW crew here :
http://www.fftw.org/install/windows.html
Whatever, this can be a helpful start point for the OSGeo4W 64 bit
package.
Those binaries already comes with .def files (but not the .lib ones).
These simplifies the process, as only
{{{
lib /machine:x64 /def:%FFTW_DEF% /out:%FFTW_IMPORTLIB%
}}}
needs to be called to generate the import lib.
Also :
* their DEF file is quite different from the one generated with the
attached script. there are symbols that are not output by dumpbin, and the
other way around (some symbols output by dumpbin do not end in the def
file). I am not so much confident about the VLC recipe I applied.
* they include in their build all possible precision flavors
(float/double/long double). I would be a client for both float and double
* [major] your build depends on msys, since the dll require something
called libwinpthread-1.dll. there is at least a missing dependency in the
setup.hint, since I don't have that on my installation. the 32bit build
was not requiring that (statically integrated?), and the fftw upstream
build does not require that either.
Do you have an opinion ?
--
Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/397#comment:4>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.
More information about the osgeo4w-dev
mailing list