Jason Bacon <jwbacon%tds.net@localhost> writes: > On 08/21/15 10:16, Greg Troxel wrote: >> Jason Bacon <jwbacon%tds.net@localhost> writes: >> >>> That was part of it, thanks. The problem is, the pkg requires >>> hdf5-c++, which does not have a buildlink3.mk, so I added it to >>> DEPENDS instead. If I include hdf5/buildlink3.mk, it seems to ignore >>> the DEPENDS entry for hdf5-c++. >> It seems that the right thing is to create a bl3 file for hdf5-c++. You >> can't use DEPENDS for things with libraries. >> >> It seems odd that hdf5-c++ doesn't have a bl3. >> >>> I worked around it with a modified hdf5 pkg that includes C++ support >>> by default. I'll put this in wip tomorrow and reach out to the >>> maintainer. >> If there is hdf5-c++, that seems likely because people want to use hdf5 >> w/o C++, so adding C++ to the regular package seems incorrect. > I'll leave that decision to the maintainer. My modified pkg including > C++ support was just meant to test the hypothesis. I still don't understand why you want to do this, becuase the hdf5-c++ package contains exactly the C++ libs, and it seems far easier to add a bl3 file (try making one with pkgtools/createbuildlink). > FYI, the FreeBSD port includes C++ support by default and Fortran > support as an option. I don't think adding C++ support requires any > additional dependencies. Besides a C++ compiler :-) It has the potential to break the package on systems with gcc 4.1 - C++ is far pickier about compiler version range. But it does sound like it doesn't prevent linking a C program with the C libs, which is the big thing.
Attachment:
pgpBzLtloIxz1.pgp
Description: PGP signature