This is the mail archive of the
mailing list for the Cygwin project.
Re: fftw3 and octave
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: Mailing List: CygWin-Apps <cygwin-apps at cygwin dot com>
- Date: Tue, 01 Apr 2008 00:02:17 -0500
- Subject: Re: fftw3 and octave
- References: <firstname.lastname@example.org> <email@example.com>
Marco Atzeri wrote:
the DLL are almost all the size of fftw3
so I can repakage as suggested, but it is
probably not worth.
Not exactly. The import libraries are almost half the size of the DLLs;
that's not insignificant. Here's what Volker is suggesting, I think
(with perhaps a few things moved around). I've put the "basic"
documentation in libfftw3-devel, and the "fancy, extra" documentation in
fftw3-doc). You'll notice that with this division, the size is
distributed across the packages -- if not evenly, then at least
'fairly'. Also, in this scheme, the 'main' package (fftw3, the one
whose name matches the -src) contains only /usr/share README-style
stuff. That's a fairly common occurance for DLL utilitity libraries.
However, putting the DLLs in a separate, standalone package is not just
about download size. It also helps with package and dependency
management, if the API of the library changes in a
Are these static libraries ? Otherwise your build
would depend on them
and you should package them for the distro.
Of course static.
The only dependency needed was fftw3
so I adopted it.
Not to look a gift horse in the mouth, but cygwin binary software is
under the GPL (or compatible open source license), because it is linked
against the cygwin1.dll.
This means that, for ALL software linked into the binaries included in
the cygwin distribution, we MUST also distribute the source.
Including static libraries.
The most convenient way to ensure this is for all dependent libraries to
ALSO be members of the cygwin distribution.
So, we usually don't allow software in the distro that links against
libaries that AREN'T part of the distro -- unless you take special care
to distribute also those EXACT sources as part of your fftw3-src package.
I'll leave this to Corinna and cgf to decide, but it seems to me that
(1) you must rebuild your official package without reliance on Qhull,
Hdf5, and qlpk/SuiteSparse, or
(2) include the EXACT Qhull/Hdf5/qlpk/SuiteSparse source code tarballs
within the fftw3-src tarball
(3) you [or someone else] must ITP these packages
or else we must continue to go without an octave maintainer. However,
that's just MHO, and I'm not in charge.