summaryrefslogtreecommitdiff
path: root/science/cdf/files/patch-src_include_cdflib.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* science/cdf: Update to 3.9.1.Stephen Montgomery-Smith2024-12-261-2/+2
| | | | | | | Change maintainer to alster@vinterdalen.se. PR: 283453 Reported by: alster@vinterdalen.se
* category/port: science/cdfStephen Montgomery-Smith2022-01-071-2/+2
| | | | - Bump portrevision of dependent port graphics/opendx.
* - Add LICENSE.Stephen Montgomery-Smith2016-10-021-2/+2
| | | | | | | - Use make makepatch. Notes: svn path=/head/; revision=423149
* - Unbreak the build on PowerPC by using correct Fif_ENTRYPOINT() macro thatAlexey Dokuchaev2015-09-101-0/+12
| | | | | | | | | | | | | | | | | | | | does not append double underscore to symbol names in binaries (previously __FreeBSD__ check was removed from the condition, but __PPC__ was left) - Rename the patch: not only it used now deprecated `+' as path separator, the patch name itself was just wrong (inconsistent with the patched file) - Remove useless PKGMESSAGE assignment, bsd.port.mk does this automatically - Improve `regression-test' target: add dependency on `build', and get rid of explicit cd'ing to ${BUILD_WRKSRC} by using -C switch of make(1) - Fix some minor whitespace bugs and reorder the knobs to make more sense I've removed BROKEN statement entirely (for all Tier-2 systems) while I've only tested it on PowerPC: it pulls quite heavy GCC 4.8 for Fortran support and I didn't want to stress our poor flame too much (This is a really slow, old machine. Be gentle). Since the bug was indeed PowerPC-specific, it is probably OK (and worth trying anyway). Notes: svn path=/head/; revision=396576
* Chase a silent update and make fetchable again.Thierry Thomas2006-02-111-11/+0
| | | | | | | | | | | | | | - our patches to support FreeBSD have been included; - support of Intel C++ and Fortran compilers for Linux has been added. Full diff available at <http://pompo.net/ports/cdf31-dist_060130_060209.diff>. Reported by: Ion-Mihai Tetcu on #bsdports Notes: svn path=/head/; revision=155791
* Common Data Format (CDF) is a conceptual data abstraction for storingThierry Thomas2006-01-281-0/+11
multi-dimensional data sets. The basic component of CDF is a software programming interface that is a device independent view of the CDF data model. The application developer is insulated from the actual physical file format for reasons of conceptual simplicity, device independence, and future expandability. CDF files created on any given platform can be transported to any other platform on to which CDF is ported and used with any CDF tools or layered applications. A comparison between CDF, netCDF, HDF and HDF5 is available at <http://cdf.gsfc.nasa.gov/html/FAQ.html>. Notes: svn path=/head/; revision=154665