openbsd-ports/java/jna/Makefile

# $OpenBSD: Makefile,v 1.24 2017/04/21 13:27:46 kurt Exp $

COMMENT=	Java Native Access (JNA)

GH_PROJECT=	jna
GH_ACCOUNT=	java-native-access
GH_TAGNAME=	4.4.0
CATEGORIES=	devel
MAINTAINER=	Jasper Lievisse Adriaanse <jasper@openbsd.org>
REVISION=	0

HOMEPAGE=	https://github.com/java-native-access/jna

# LGPLv2.1+
PERMIT_PACKAGE_CDROM=	Yes

MODULES=	java
MODJAVA_VER=	1.6+
MODJAVA_BUILD=	ant

# use the system libffi
MODJAVA_BUILD_ARGS +=-Ddynlink.native=true

# build.xml specifically wants gmake (and ggrep)
USE_GMAKE=	Yes

BUILD_DEPENDS=	sysutils/ggrep
LIB_DEPENDS=	devel/libffi
# clojure needs to have the jna.jar installed
TEST_DEPENDS=	${BASE_PKGPATH} \
		lang/clojure

MAKE_ENV=	CC="${CC}" \
		PORTS_CFLAGS="${CFLAGS}"

GNU_ARCH=	${ARCH:S/amd64/x86-64/:S/i386/x86/}

# XXX: remove stale distribution file
post-extract:
	rm ${WRKSRC}/native/libffi/src/powerpc/linux64_closure.S.orig

pre-configure:
	sed -i -e 's,-Wno-unknown-warning-option,,' \
		-e 's,-Wno-clobbered,,' ${WRKSRC}/native/Makefile

do-install:
	${INSTALL_DATA_DIR} ${MODJAVA_JAR_DIR} ${MODJAVA_DOC_DIR}/jna/
	${INSTALL_DATA} ${WRKSRC}/build/openbsd-${GNU_ARCH}.jar \
		${MODJAVA_JAR_DIR}/jna-platform.jar
	${INSTALL_DATA} ${WRKSRC}/build/jna*.jar ${MODJAVA_JAR_DIR}
	cp -r ${WRKSRC}/doc/javadoc ${MODJAVA_DOC_DIR}

do-test:
	cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${LOCALBASE}/bin/ant \
		${MODJAVA_BUILD_ARGS} test
	${SHELL} ${FILESDIR}/test.sh

.include <bsd.port.mk>
- disconnect devel/jdk/1.7 from the build - adjust java.port.mk so all 1.7 and lower ports now build with 1.8 - bump revision on affected ports okay sthen@, ian@, landry@ 2017-04-21 13:27:46 +00:00			`# $OpenBSD: Makefile,v 1.24 2017/04/21 13:27:46 kurt Exp $`
import jna 3.2.7 JNA provides Java programs easy access to native shared libraries without writing anything but Java code -- no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. ok aja@ 2011-08-29 15:07:32 +00:00
			`COMMENT= Java Native Access (JNA)`

- update to jna-4.1.0 - update homepage - switch to using GH_* tested with clojure 2015-09-01 19:29:22 +00:00			`GH_PROJECT= jna`
			`GH_ACCOUNT= java-native-access`
update to jna-4.4.0 2017-03-26 12:45:27 +00:00			`GH_TAGNAME= 4.4.0`
- bump REVISION after recent java.port.mk change 2011-08-30 17:16:35 +00:00			`CATEGORIES= devel`
- take maintainership 2011-08-30 12:03:56 +00:00			`MAINTAINER= Jasper Lievisse Adriaanse <jasper@openbsd.org>`
- disconnect devel/jdk/1.7 from the build - adjust java.port.mk so all 1.7 and lower ports now build with 1.8 - bump revision on affected ports okay sthen@, ian@, landry@ 2017-04-21 13:27:46 +00:00			`REVISION= 0`
- take maintainership 2011-08-30 12:03:56 +00:00
- update to jna-4.1.0 - update homepage - switch to using GH_* tested with clojure 2015-09-01 19:29:22 +00:00			`HOMEPAGE= https://github.com/java-native-access/jna`
import jna 3.2.7 JNA provides Java programs easy access to native shared libraries without writing anything but Java code -- no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. ok aja@ 2011-08-29 15:07:32 +00:00
			`# LGPLv2.1+`
			`PERMIT_PACKAGE_CDROM= Yes`

			`MODULES= java`
			`MODJAVA_VER= 1.6+`
- switch to MODJAVA_BUILD - add comment about gmake (requested by sthen@) - don't use a handrolled MODJAVA_{DOC,JAR}_DIR 2011-09-01 08:05:05 +00:00			`MODJAVA_BUILD= ant`
import jna 3.2.7 JNA provides Java programs easy access to native shared libraries without writing anything but Java code -- no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. ok aja@ 2011-08-29 15:07:32 +00:00
- update to jna-4.2.0 - switch to using the system libffi 2015-09-18 18:36:27 +00:00			`# use the system libffi`
			`MODJAVA_BUILD_ARGS +=-Ddynlink.native=true`

- Use a rerolled distfile that includes openbsd native libs for both amd64 and i386. Makes installed jna.jar include both archs. okay jasper@ 2013-03-17 14:02:11 +00:00			`# build.xml specifically wants gmake (and ggrep)`
- take maintainership 2011-08-30 12:03:56 +00:00			`USE_GMAKE= Yes`

- switch to MODJAVA_BUILD - add comment about gmake (requested by sthen@) - don't use a handrolled MODJAVA_{DOC,JAR}_DIR 2011-09-01 08:05:05 +00:00			`BUILD_DEPENDS= sysutils/ggrep`
- update to jna-4.2.0 - switch to using the system libffi 2015-09-18 18:36:27 +00:00			`LIB_DEPENDS= devel/libffi`
add extended testcase based on clojure 2015-10-24 14:22:14 +00:00			`# clojure needs to have the jna.jar installed`
			`TEST_DEPENDS= ${BASE_PKGPATH} \`
			`lang/clojure`
import jna 3.2.7 JNA provides Java programs easy access to native shared libraries without writing anything but Java code -- no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. ok aja@ 2011-08-29 15:07:32 +00:00
Honour CC/CFLAGS 2017-03-06 21:19:20 +00:00			`MAKE_ENV= CC="${CC}" \`
			`PORTS_CFLAGS="${CFLAGS}"`

fix java/jna packaging on i386 2015-09-04 21:22:29 +00:00			`GNU_ARCH= ${ARCH:S/amd64/x86-64/:S/i386/x86/}`
fix build issue on i386 ok jasper@ (maintainer) 2011-09-12 12:50:24 +00:00
update to jna-4.2.1 2015-10-24 14:08:41 +00:00			`# XXX: remove stale distribution file`
			`post-extract:`
update to jna-4.2.2 2016-04-18 17:33:11 +00:00			`rm ${WRKSRC}/native/libffi/src/powerpc/linux64_closure.S.orig`
update to jna-4.2.1 2015-10-24 14:08:41 +00:00
update to jna-4.3.0 2017-02-25 15:05:21 +00:00			`pre-configure:`
			`sed -i -e 's,-Wno-unknown-warning-option,,' \`
			`-e 's,-Wno-clobbered,,' ${WRKSRC}/native/Makefile`

import jna 3.2.7 JNA provides Java programs easy access to native shared libraries without writing anything but Java code -- no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. ok aja@ 2011-08-29 15:07:32 +00:00			`do-install:`
- switch to MODJAVA_BUILD - add comment about gmake (requested by sthen@) - don't use a handrolled MODJAVA_{DOC,JAR}_DIR 2011-09-01 08:05:05 +00:00			`${INSTALL_DATA_DIR} ${MODJAVA_JAR_DIR} ${MODJAVA_DOC_DIR}/jna/`
- update to jna-4.1.0 - update homepage - switch to using GH_* tested with clojure 2015-09-01 19:29:22 +00:00			`${INSTALL_DATA} ${WRKSRC}/build/openbsd-${GNU_ARCH}.jar \`
- switch to MODJAVA_BUILD - add comment about gmake (requested by sthen@) - don't use a handrolled MODJAVA_{DOC,JAR}_DIR 2011-09-01 08:05:05 +00:00			`${MODJAVA_JAR_DIR}/jna-platform.jar`
- update to jna-4.1.0 - update homepage - switch to using GH_* tested with clojure 2015-09-01 19:29:22 +00:00			`${INSTALL_DATA} ${WRKSRC}/build/jna*.jar ${MODJAVA_JAR_DIR}`
update to jna-4.3.0 2017-02-25 15:05:21 +00:00			`cp -r ${WRKSRC}/doc/javadoc ${MODJAVA_DOC_DIR}`
import jna 3.2.7 JNA provides Java programs easy access to native shared libraries without writing anything but Java code -- no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. ok aja@ 2011-08-29 15:07:32 +00:00
PERMIT_* / REGRESS -> TEST sweep 2013-03-11 11:10:51 +00:00			`do-test:`
- update to jna-4.2.0 - switch to using the system libffi 2015-09-18 18:36:27 +00:00			`cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${LOCALBASE}/bin/ant \`
			`${MODJAVA_BUILD_ARGS} test`
add extended testcase based on clojure 2015-10-24 14:22:14 +00:00			`${SHELL} ${FILESDIR}/test.sh`
import jna 3.2.7 JNA provides Java programs easy access to native shared libraries without writing anything but Java code -- no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. ok aja@ 2011-08-29 15:07:32 +00:00
			`.include <bsd.port.mk>`