-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Marco Atzeri wrote: | I put the hdf5 in a separate directory just to have | a more clean /usr/include structure as | hdf5.h call tens of other HDF5 header.
The problem is that dependent packages expect them in /usr/include, and have no way of knowing that they are elsewhere, as hdf5 uses neither pkg-config nor its own -config script. For example, try building octave-fltk: http://cygwin-ports.cvs.sourceforge.net/cygwin-ports/ports/octave/fltk/ You'll get an error because octave/ov.h can't find hdf5.h. | I built the extensions of octave-forge with just | CPPFLAGS="-I/usr/include/hdf5" | before calling octave for the pkg install. Yes, but *every* package requiring hdf5 directly or indirectly will need this, which is an unnecessary inconvenience. | If you really need I will modify the package, | but I think that /usr/include/hdf5 | is a more clean solution You'll find it's best to stick with upstream packaging rules and precedent set by other distros. It will make things much easier for yourself and others. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkhYBdkACgkQpiWmPGlmQSOUkACgyP7mPdNxLPtu6bVf/zMdsaTL hPQAn3eoVBapnAtcazdZZceAGSZWKqBh =TGm5 -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
