2001-03-10 21:35:18 +01:00
|
|
|
# New ports collection makefile for: fpx
|
|
|
|
# Date created: Jan 10 2001
|
|
|
|
# Whom: Mikhail Teterin <mi@aldan.algebra.com>
|
|
|
|
#
|
|
|
|
# $FreeBSD$
|
|
|
|
#
|
|
|
|
|
2002-02-13 07:30:43 +01:00
|
|
|
PORTNAME= libfpx
|
2005-03-01 18:43:34 +01:00
|
|
|
PORTVERSION= 1.2.0.12
|
2012-02-08 18:20:14 +01:00
|
|
|
PORTREVISION= 2
|
2001-03-10 21:35:18 +01:00
|
|
|
CATEGORIES= graphics
|
2006-10-27 21:44:03 +02:00
|
|
|
MASTER_SITES= ${MASTER_SITE_LOCAL}
|
|
|
|
MASTER_SITE_SUBDIR= ehaupt
|
2012-02-08 18:20:14 +01:00
|
|
|
|
2007-11-02 13:42:07 +01:00
|
|
|
PATCHFILES= fpx.mega-patch.2007-11-01.bz2
|
|
|
|
PATCH_SITES= http://aldan.algebra.com/~mi/
|
2001-03-10 21:35:18 +01:00
|
|
|
|
|
|
|
MAINTAINER= mi@aldan.algebra.com
|
2003-03-07 07:14:21 +01:00
|
|
|
COMMENT= Library routines for working with Flashpix images
|
2001-03-10 21:35:18 +01:00
|
|
|
|
2003-04-24 01:30:59 +02:00
|
|
|
USE_BZIP2= yes
|
2001-03-10 21:35:18 +01:00
|
|
|
|
This package has a controversial history. It was originally "given" to
the ImageMagick team, where Bob Friesenhahn made it work with IM.
Since then, Bob and other developers forked GraphicsMagick. libfpx
remained unchanged until January 2005, when ImageMagick released an
updated tar-ball with a patch applied. The release was botched (missing
a subdirectory) and I changed the port to use the old tar-ball on
GraphicsMagick's site and apply the same patch.
Since then, GraphicsMagick replaced the old 1.2.0.9 tarball with the new
1.2.0.10, where the patch is applied. On the same date, ImageMagick,
not to be outdone, "released" 1.2.0.11, WHICH IS NO DIFFERENT from
GraphicsMagick's version, except for libtool/configure soup.
I'm now switching the port to ImageMagick's mirrors again, simply
because they seem to have better bandwidth.
I must add, for the record, that ImageMagick team's behavior appears
rather dubious and unscrupulous in this incident. There was no need to
"release" their own tarball, especially considering, that some sources
are marked as "GraphicsMagick" (an embarassing oversight). I also
found, that those of my postings on ImageMagick's support forum, which
mentioned GraphicsMagick, were misteriously removed from the board
shortly after posting...
This update is made neccessary by there being no MASTER_SITES for the
original 1.2.0.9 tarball left. While at it, however, I also remove the
jpeg-dependency -- libfpx does not, actually, use it.
Prompted by: pointyhat (kris)
2005-02-14 21:59:50 +01:00
|
|
|
post-patch:
|
2007-11-02 13:42:07 +01:00
|
|
|
${RM} ${WRKSRC}/ri_image/wchar.c ${WRKSRC}/fpx/fpxlib.h
|
This package has a controversial history. It was originally "given" to
the ImageMagick team, where Bob Friesenhahn made it work with IM.
Since then, Bob and other developers forked GraphicsMagick. libfpx
remained unchanged until January 2005, when ImageMagick released an
updated tar-ball with a patch applied. The release was botched (missing
a subdirectory) and I changed the port to use the old tar-ball on
GraphicsMagick's site and apply the same patch.
Since then, GraphicsMagick replaced the old 1.2.0.9 tarball with the new
1.2.0.10, where the patch is applied. On the same date, ImageMagick,
not to be outdone, "released" 1.2.0.11, WHICH IS NO DIFFERENT from
GraphicsMagick's version, except for libtool/configure soup.
I'm now switching the port to ImageMagick's mirrors again, simply
because they seem to have better bandwidth.
I must add, for the record, that ImageMagick team's behavior appears
rather dubious and unscrupulous in this incident. There was no need to
"release" their own tarball, especially considering, that some sources
are marked as "GraphicsMagick" (an embarassing oversight). I also
found, that those of my postings on ImageMagick's support forum, which
mentioned GraphicsMagick, were misteriously removed from the board
shortly after posting...
This update is made neccessary by there being no MASTER_SITES for the
original 1.2.0.9 tarball left. While at it, however, I also remove the
jpeg-dependency -- libfpx does not, actually, use it.
Prompted by: pointyhat (kris)
2005-02-14 21:59:50 +01:00
|
|
|
|
2012-02-08 18:20:14 +01:00
|
|
|
PLIST_FILES=lib/libfpx.so.2 lib/libfpx.so lib/libfpx.a include/fpxlib.h
|
2007-01-27 15:04:44 +01:00
|
|
|
USE_LDCONFIG= yes
|
2001-03-10 21:35:18 +01:00
|
|
|
MAKEFILE= ${FILESDIR}/Makefile.bsd
|
2012-02-08 18:20:14 +01:00
|
|
|
MAKE_JOBS_SAFE= yes
|
2001-03-10 21:35:18 +01:00
|
|
|
|
2005-01-26 00:19:47 +01:00
|
|
|
.include <bsd.port.mk>
|
2007-11-02 13:42:07 +01:00
|
|
|
|
|
|
|
# We want the port's Makefile to build compiler-flags from scratch
|
|
|
|
# (based on WARNS= in particular) instead of being influenced by
|
|
|
|
# the environment... There is no obvious way to prevent bsd.port.mk
|
|
|
|
# from adding CFLAGS and CXXFLAGS to the build environment, so we
|
|
|
|
# remove them here.
|
|
|
|
MAKE_ENV:= ${MAKE_ENV:NCFLAGS=*:NCXXFLAGS=*}
|