cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1438e4ca7e
openbsd-ports/devel/haddock/Makefile

77 lines
1.9 KiB
Makefile
Raw Normal View History

convert libiconv to new wantlib
2010-11-06 06:18:38 -04:00
# $OpenBSD: Makefile,v 1.25 2010/11/06 10:18:38 espie Exp $
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
Include the Haddock API, but put it into its own subpackage (hs-haddock). This will be needed by leksah.
2010-06-18 16:42:03 -04:00
COMMENT-main = documentation-generation tool for Haskell libraries
COMMENT-lib = haddock library
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
DISTNAME = haddock-2.7.2
Switch to REVISION and new WANTLIB/LIB_DEPENDS style.
2010-07-17 09:54:30 -04:00
PKGNAME-main = ${DISTNAME}
- regen plist after recent ghc.port.mk change - adjust @exec/@unexec accordingly "just go ahead" kili@
2010-10-28 09:51:00 -04:00
REVISION-main = 4
Include the Haddock API, but put it into its own subpackage (hs-haddock). This will be needed by leksah.
2010-06-18 16:42:03 -04:00
PKGNAME-lib = hs-${DISTNAME}
bumpski
2010-11-03 18:12:01 -04:00
REVISION-lib = 2
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
CATEGORIES = devel
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
HOMEPAGE = http://www.haskell.org/haddock/
Update to 0.8 to make it build with ghc-6.6.1.
2007-07-21 13:20:20 -04:00
Include the Haddock API, but put it into its own subpackage (hs-haddock). This will be needed by leksah.
2010-06-18 16:42:03 -04:00
MULTI_PACKAGES = -main -lib
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
# BSD3
PERMIT_PACKAGE_CDROM = Yes
PERMIT_PACKAGE_FTP = Yes
PERMIT_DISTFILES_CDROM =Yes
PERMIT_DISTFILES_FTP = Yes
Update to 0.8 to make it build with ghc-6.6.1.
2007-07-21 13:20:20 -04:00
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
# This pseudo flavor is needed to let ghc extract the haddock sources
# without pulling in haddocks own build dependencies (which would
# include ghc).
PSEUDO_FLAVORS = no_deps
FLAVOR ?=
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
.if ! ${FLAVOR:L:Mno_deps}
MODULES = lang/ghc converters/libiconv
Include the Haddock API, but put it into its own subpackage (hs-haddock). This will be needed by leksah.
2010-06-18 16:42:03 -04:00
MODGHC_BUILD = cabal hackage register
Update to haddock-0.5, build docs from sgml source, cleanup From: Don Stewart <dons@cse.unsw.edu.au>
2003-07-30 21:11:14 -04:00
Include the Haddock API, but put it into its own subpackage (hs-haddock). This will be needed by leksah.
2010-06-18 16:42:03 -04:00
LIB_DEPENDS-lib =
LIB_DEPENDS-main = ${LIB_DEPENDS} \
Switch to REVISION and new WANTLIB/LIB_DEPENDS style.
2010-07-17 09:54:30 -04:00
::devel/gmp
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
convert libiconv to new wantlib
2010-11-06 06:18:38 -04:00
WANTLIB-lib =
WANTLIB-main = ${WANTLIB} \
c gmp m pthread util
Move WANTLIB-main into the ! ${FLAVOR:L:Mno_deps} block, so the no_deps FLAVOR has really no dependencies. Add an always failing do-build for no_deps that tells people why this FLAVOR exists. "makes sense" jakemsr@, who initlally sent a different diff
2010-08-26 18:05:05 -04:00
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
BUILD_DEPENDS += ::devel/alex \
::devel/happy \
Add gmp dependency. Move hs-ghc-paths from RUN_DEPENDS to BUILD_DEPENDS. Bump.
2010-06-15 13:38:17 -04:00
::devel/hs-ghc-paths \
Require ghc-doc to get all links enabled.
2010-06-18 17:34:23 -04:00
::lang/ghc,-doc \
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
::textproc/docbook \
::textproc/docbook-xsl \
::textproc/libxslt \
${RUN_DEPENDS}
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
Update to 0.8 to make it build with ghc-6.6.1.
2007-07-21 13:20:20 -04:00
# Required for building the documentation:
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
USE_GMAKE = Yes
CONFIGURE_STYLE = autoconf no-autoheader
AUTOCONF_VERSION = 2.61
AUTOCONF_DIR = ${WRKSRC}/doc
WRKCONF = ${AUTOCONF_DIR}
.else
MASTER_SITES = http://hackage.haskell.org/packages/archive/${DISTNAME:S,-,/,}/
Move WANTLIB-main into the ! ${FLAVOR:L:Mno_deps} block, so the no_deps FLAVOR has really no dependencies. Add an always failing do-build for no_deps that tells people why this FLAVOR exists. "makes sense" jakemsr@, who initlally sent a different diff
2010-08-26 18:05:05 -04:00
do-build:
@echo "*** The no_deps FLAVOR is not meant to be built at all, it is"
@echo "*** only used by lang/ghc to get a copy of the haddock sources."
@false
Update to haddock-2.7.2
2010-04-22 17:49:12 -04:00
.endif
post-build:
Don't use runhaskell and unbreak for amd64.
2007-08-01 17:59:55 -04:00
@cd ${WRKBUILD}/doc && exec ${SETENV} ${MAKE_ENV} ${MAKE_PROGRAM} html
Include the Haddock API, but put it into its own subpackage (hs-haddock). This will be needed by leksah.
2010-06-18 16:42:03 -04:00
@cd ${WRKBUILD} && exec ${SETENV} ${MAKE_ENV} \
Oops. I forgot that Haskell people are bad on bootstrapping. Force the build to use the inplace haddock for building the haddock documentation.
2010-06-18 17:05:06 -04:00
${MODGHC_SETUP_PROG} \
--with-haddock=${WRKBUILD}/dist/build/haddock/haddock \
haddock --haddock-option=-l${WRKBUILD}
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
Update to 0.8 to make it build with ghc-6.6.1.
2007-07-21 13:20:20 -04:00
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/doc
Don't use runhaskell and unbreak for amd64.
2007-08-01 17:59:55 -04:00
cd ${WRKBUILD}/doc && umask 022 && pax -rw haddock ${PREFIX}/share/doc
initial import of haddock-0.4, from Don Stewart <dons at cse.unsw.edu.au> -- Haddock is a tool for automatically generating documentation from annotated Haskell source code. It is primary intended for documenting libraries, but it should be useful for any kind of Haskell code. Like other systems, Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked.
2003-07-24 20:26:13 -04:00
.include <bsd.port.mk>
Reference in New Issue Copy Permalink