kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/mk/java-vm.mk

318 lines
9.7 KiB
Makefile
Raw Normal View History

Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
# $NetBSD: java-vm.mk,v 1.45 2006/04/06 06:23:06 reed Exp $
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
#
# This Makefile fragment handles Java dependencies and make variables,
# and is meant to be included by packages that require Java either at
Move java.mk to java-vm.mk to avoid name conflict with devel/mk-files as suggested by Simon J. Gerraty.
2002-12-26 21:52:09 +01:00
# build-time or at run-time. java-vm.mk will:
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
#
# * set PKG_JVM and PKG_JAVA_HOME to the name of the JVM used and
# to the directory in which the JVM is installed, respectively;
#
# * add a full dependency on the JRE and possibly a build dependency
Clarify comments to more explicitly note how to _not_ add the dependency on the JDK.
2003-05-25 20:39:12 +02:00
# on the JDK.
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
#
Clarify comments to more explicitly note how to _not_ add the dependency on the JDK.
2003-05-25 20:39:12 +02:00
# There are four variables used to tweak the JVM selection:
#
# USE_JAVA is used to note whether a build-time dependency on the JDK is
# added (the default). If USE_JAVA is set to "run", then we _don't_
# add the dependency on the JDK. The default value is "yes".
USE_JAVA2 is used to note that the package requires a Java2 implementation. It's undefined by default, but may be set to "yes".
2002-12-31 15:42:21 +01:00
#
# USE_JAVA2 is used to note that the package requires a Java2 implementation.
Allow USE_JAVA2 to (optionally) be set to 1.4 or 1.5, and use in tomcat55
2005-06-02 12:07:48 +02:00
# It's undefined by default, but may be set to "yes" or to one of
# 1.4 or 1.5
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
#
# PKG_JVM_DEFAULT is a user-settable variable whose value is the default
# JVM to use.
#
# PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as
# possible dependencies for the package.
Move java.mk to java-vm.mk to avoid name conflict with devel/mk-files as suggested by Simon J. Gerraty.
2002-12-26 21:52:09 +01:00
.if !defined(JAVA_VM_MK)
JAVA_VM_MK= # defined
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
.include "../../mk/bsd.prefs.mk"
# By default, assume we need the JDK.
Allow for strangely-cased USE_JAVA values.
2002-12-31 15:39:59 +01:00
USE_JAVA?= yes
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
.if !empty(USE_JAVA:M[rR][uU][nN])
USE_JAVA= run
.endif
PKG_JVM_DEFAULT?= # empty
Knock off a TODO item: when generating the internal list of acceptable JVMs from the package-provided PKG_JVM_ACCEPTED list, filter out those JVMs that aren't available for the current platform. This allows a package to simply list all JVMs that may be used to build it in PKG_JVM_ACCEPTED, regardless of platform issues, instead of having to construct a different PKG_JVM_ACCEPTED based on the platform we are using.
2002-10-14 14:10:54 +02:00
PKG_JVMS_ACCEPTED?= ${_PKG_JVMS}
Allow for strangely-cased USE_JAVA values.
2002-12-31 15:39:59 +01:00
# This is a list of all of the JVMs that may be used with java-vm.mk.
#
Allow USE_JAVA2 to (optionally) be set to 1.4 or 1.5, and use in tomcat55
2005-06-02 12:07:48 +02:00
.if defined(USE_JAVA2) && ${USE_JAVA2} == "1.5"
_PKG_JVMS?= sun-jdk15
.elif defined(USE_JAVA2) && ${USE_JAVA2} == "1.4"
_PKG_JVMS?= sun-jdk14 sun-jdk15 jdk14
.elif defined(USE_JAVA2) && !empty(USE_JAVA2:M[yY][eE][sS])
Remove wonka support, now that wonka package is gone. Noted by schmonz@.
2005-04-19 13:54:50 +02:00
_PKG_JVMS?= sun-jdk13 sun-jdk14 blackdown-jdk13 kaffe \
Disable win32-jdk for now. It doesn't play well with bulk builds yet.
2005-01-12 18:23:46 +01:00
sun-jdk15 jdk14 # win32-jdk
USE_JAVA2 is used to note that the package requires a Java2 implementation. It's undefined by default, but may be set to "yes".
2002-12-31 15:42:21 +01:00
.else
Add buildlink3 bits.
2004-05-02 22:30:44 +02:00
_PKG_JVMS?= jdk sun-jdk13 sun-jdk14 blackdown-jdk13 kaffe \
Remove wonka support, now that wonka package is gone. Noted by schmonz@.
2005-04-19 13:54:50 +02:00
sun-jdk15 jdk14 # win32-jdk
USE_JAVA2 is used to note that the package requires a Java2 implementation. It's undefined by default, but may be set to "yes".
2002-12-31 15:42:21 +01:00
.endif
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
# To be deprecated: if PKG_JVM is explicitly set, then use it as the
# default JVM. Note that this has lower precedence than PKG_JVM_DEFAULT.
#
.if defined(PKG_JVM)
. if !empty(PKG_JVM)
_PKG_JVM_DEFAULT:= ${PKG_JVM}
. endif
.endif
# Set the default JVM for this platform.
#
.if !empty(PKG_JVM_DEFAULT)
_PKG_JVM_DEFAULT= ${PKG_JVM_DEFAULT}
.endif
.if !defined(_PKG_JVM_DEFAULT)
. if !empty(MACHINE_PLATFORM:MNetBSD-*-i386) || \
!empty(MACHINE_PLATFORM:MLinux-*-i[3456]86)
_PKG_JVM_DEFAULT?= jdk
. elif !empty(MACHINE_PLATFORM:MNetBSD-*-powerpc)
_PKG_JVM_DEFAULT?= blackdown-jdk13
. elif !empty(MACHINE_PLATFORM:MDarwin-*-*)
_PKG_JVM_DEFAULT?= sun-jdk
Disable win32-jdk for now. It doesn't play well with bulk builds yet.
2005-01-12 18:23:46 +01:00
#. elif !empty(MACHINE_PLATFORM:MInterix-*-*)
#_PKG_JVM_DEFAULT?= win32-jdk
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
. else
_PKG_JVM_DEFAULT?= kaffe
. endif
.endif
Knock off a TODO item: when generating the internal list of acceptable JVMs from the package-provided PKG_JVM_ACCEPTED list, filter out those JVMs that aren't available for the current platform. This allows a package to simply list all JVMs that may be used to build it in PKG_JVM_ACCEPTED, regardless of platform issues, instead of having to construct a different PKG_JVM_ACCEPTED based on the platform we are using.
2002-10-14 14:10:54 +02:00
# These lists are copied from the JVM package Makefiles.
_ONLY_FOR_PLATFORMS.blackdown-jdk13= \
NetBSD-*-i386 NetBSD-*-powerpc NetBSD-*-sparc \
First step at reworking Linux binary packages. Change most pkgs to depend on either emulators/suse_linux/Makefile.application (normal pkgs) or Makefile.common (suse91 and suse themselves) to filter out Operating Systems without Linux ABI support. Use CPU masks to limit the pkg to supported platforms.
2005-12-12 15:43:23 +01:00
Linux-*-i[3-6]86 Linux-*-powerpc Linux-*-sparc \
DragonFly-*-i386
Allow for strangely-cased USE_JAVA values.
2002-12-31 15:39:59 +01:00
.if !empty(USE_JAVA:M[rR][uU][nN])
Knock off a TODO item: when generating the internal list of acceptable JVMs from the package-provided PKG_JVM_ACCEPTED list, filter out those JVMs that aren't available for the current platform. This allows a package to simply list all JVMs that may be used to build it in PKG_JVM_ACCEPTED, regardless of platform issues, instead of having to construct a different PKG_JVM_ACCEPTED based on the platform we are using.
2002-10-14 14:10:54 +02:00
_ONLY_FOR_PLATFORMS.blackdown-jdk13+= \
NetBSD-*-arm Linux-*-arm
.endif
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
_ONLY_FOR_PLATFORMS.jdk= \
First step at reworking Linux binary packages. Change most pkgs to depend on either emulators/suse_linux/Makefile.application (normal pkgs) or Makefile.common (suse91 and suse themselves) to filter out Operating Systems without Linux ABI support. Use CPU masks to limit the pkg to supported platforms.
2005-12-12 15:43:23 +01:00
NetBSD-*-i386 Linux-*-i[3-6]86 DragonFly-*-i386
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
_ONLY_FOR_PLATFORMS.jdk14= \
First step at reworking Linux binary packages. Change most pkgs to depend on either emulators/suse_linux/Makefile.application (normal pkgs) or Makefile.common (suse91 and suse themselves) to filter out Operating Systems without Linux ABI support. Use CPU masks to limit the pkg to supported platforms.
2005-12-12 15:43:23 +01:00
NetBSD-[2-9].*-i386 DragonFly-*-i386
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
_ONLY_FOR_PLATFORMS.kaffe= \
*-*-alpha *-*-arm *-*-arm32 *-*-i386 *-*-m68k *-*-mips* *-*-sparc *-*-powerpc
Knock off a TODO item: when generating the internal list of acceptable JVMs from the package-provided PKG_JVM_ACCEPTED list, filter out those JVMs that aren't available for the current platform. This allows a package to simply list all JVMs that may be used to build it in PKG_JVM_ACCEPTED, regardless of platform issues, instead of having to construct a different PKG_JVM_ACCEPTED based on the platform we are using.
2002-10-14 14:10:54 +02:00
_ONLY_FOR_PLATFORMS.sun-jdk13= \
First step at reworking Linux binary packages. Change most pkgs to depend on either emulators/suse_linux/Makefile.application (normal pkgs) or Makefile.common (suse91 and suse themselves) to filter out Operating Systems without Linux ABI support. Use CPU masks to limit the pkg to supported platforms.
2005-12-12 15:43:23 +01:00
NetBSD-*-i386 Linux-*-i[3-6]86 Darwin-*-* DragonFly-*-i386
Knock off a TODO item: when generating the internal list of acceptable JVMs from the package-provided PKG_JVM_ACCEPTED list, filter out those JVMs that aren't available for the current platform. This allows a package to simply list all JVMs that may be used to build it in PKG_JVM_ACCEPTED, regardless of platform issues, instead of having to construct a different PKG_JVM_ACCEPTED based on the platform we are using.
2002-10-14 14:10:54 +02:00
_ONLY_FOR_PLATFORMS.sun-jdk14= \
Allow PKG_JVM=jdk14 (once a buildlink file has been added to wip/jdk14)
2004-06-03 22:19:08 +02:00
NetBSD-1.5Z[A-Z]-i386 NetBSD-1.[6-9]*-i386 NetBSD-[2-9].*-i386 \
First step at reworking Linux binary packages. Change most pkgs to depend on either emulators/suse_linux/Makefile.application (normal pkgs) or Makefile.common (suse91 and suse themselves) to filter out Operating Systems without Linux ABI support. Use CPU masks to limit the pkg to supported platforms.
2005-12-12 15:43:23 +01:00
Linux-*-i[3-6]86 DragonFly-*-i386
Add and enable {jdk,jre}15
2004-10-01 01:50:33 +02:00
_ONLY_FOR_PLATFORMS.sun-jdk15= \
NetBSD-1.5Z[A-Z]-i386 NetBSD-1.[6-9]*-i386 NetBSD-[2-9].*-i386 \
First step at reworking Linux binary packages. Change most pkgs to depend on either emulators/suse_linux/Makefile.application (normal pkgs) or Makefile.common (suse91 and suse themselves) to filter out Operating Systems without Linux ABI support. Use CPU masks to limit the pkg to supported platforms.
2005-12-12 15:43:23 +01:00
Linux-*-i[3-6]86 DragonFly-*-i386
Disable win32-jdk for now. It doesn't play well with bulk builds yet.
2005-01-12 18:23:46 +01:00
#_ONLY_FOR_PLATFORMS.win32-jdk= \
# Interix-*-*
Knock off a TODO item: when generating the internal list of acceptable JVMs from the package-provided PKG_JVM_ACCEPTED list, filter out those JVMs that aren't available for the current platform. This allows a package to simply list all JVMs that may be used to build it in PKG_JVM_ACCEPTED, regardless of platform issues, instead of having to construct a different PKG_JVM_ACCEPTED based on the platform we are using.
2002-10-14 14:10:54 +02:00
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
# Set the accepted JVMs for this platform.
Knock off a TODO item: when generating the internal list of acceptable JVMs from the package-provided PKG_JVM_ACCEPTED list, filter out those JVMs that aren't available for the current platform. This allows a package to simply list all JVMs that may be used to build it in PKG_JVM_ACCEPTED, regardless of platform issues, instead of having to construct a different PKG_JVM_ACCEPTED based on the platform we are using.
2002-10-14 14:10:54 +02:00
.for _jvm_ in ${_PKG_JVMS}
. for _pattern_ in ${_ONLY_FOR_PLATFORMS.${_jvm_}}
. if !empty(MACHINE_PLATFORM:M${_pattern_})
_PKG_JVMS_ACCEPTED+= ${PKG_JVMS_ACCEPTED:M${_jvm_}}
. endif
. endfor
.endfor
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
_JAVA_PKGBASE.blackdown-jdk13= blackdown-jdk13
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
_JAVA_PKGBASE.jdk= jdk
Allow PKG_JVM=jdk14 (once a buildlink file has been added to wip/jdk14)
2004-06-03 22:19:08 +02:00
_JAVA_PKGBASE.jdk14= jdk14
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
_JAVA_PKGBASE.kaffe= kaffe
Check for the JRE and not the SDK package to figure which version of the Sun Java package is installed.
2005-04-20 15:17:40 +02:00
_JAVA_PKGBASE.sun-jdk13= sun-jre13
_JAVA_PKGBASE.sun-jdk14= sun-jre14
_JAVA_PKGBASE.sun-jdk15= sun-jre15
Disable win32-jdk for now. It doesn't play well with bulk builds yet.
2005-01-12 18:23:46 +01:00
#_JAVA_PKGBASE.win32-jdk= win32-jdk
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
# Mark the acceptable JVMs and check which JVM packages are installed.
.for _jvm_ in ${_PKG_JVMS_ACCEPTED}
_PKG_JVM_OK.${_jvm_}= yes
_PKG_JVM_INSTALLED.${_jvm_}!= \
if ${PKG_INFO} -qe ${_JAVA_PKGBASE.${_jvm_}}; then \
${ECHO} yes; \
else \
${ECHO} no; \
fi
.endfor
Add and enable {jdk,jre}15
2004-10-01 01:50:33 +02:00
# Convert "sun-jdk" into "sun-jdk1[345]" depending on the
# platform. Recent versions of NetBSD and Linux can use the 1.3-1.5
# versions of the Sun JDK, so default to the newer installed one.
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
#
.if ${_PKG_JVM_DEFAULT} == "sun-jdk"
sun-jdk defaults to sun-jdk14, but sun-jdk14 does not work reliably on NetBSD/i386 1.6. I_believe_ it started working around the point scheduler activations were imported, so give sun-jdk14 to 1.6M and later, otherwise sun-jdk13.
2003-05-09 13:31:46 +02:00
. if !empty(MACHINE_PLATFORM:MNetBSD-1.6[M-Z]*-i386) || \
Allow PKG_JVM=jdk14 (once a buildlink file has been added to wip/jdk14)
2004-06-03 22:19:08 +02:00
!empty(MACHINE_PLATFORM:MNetBSD-[2-9].*-i386) || \
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
!empty(MACHINE_PLATFORM:MLinux-*-i[3456]86)
Add and enable {jdk,jre}15
2004-10-01 01:50:33 +02:00
. if defined(_PKG_JVM_INSTALLED.sun-jdk15) && \
(${_PKG_JVM_INSTALLED.sun-jdk15} == "yes")
_PKG_JVM_DEFAULT= sun-jdk15
. elif defined(_PKG_JVM_INSTALLED.sun-jdk14) && \
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
(${_PKG_JVM_INSTALLED.sun-jdk14} == "yes")
_PKG_JVM_DEFAULT= sun-jdk14
. elif defined(_PKG_JVM_INSTALLED.sun-jdk13) && \
(${_PKG_JVM_INSTALLED.sun-jdk13} == "yes")
_PKG_JVM_DEFAULT= sun-jdk13
. else
Add and enable {jdk,jre}15
2004-10-01 01:50:33 +02:00
_PKG_JVM_DEFAULT= sun-jdk15
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
. endif
. elif !empty(MACHINE_PLATFORM:MNetBSD-*-i386) || \
!empty(MACHINE_PLATFORM:MDarwin-*-*)
_PKG_JVM_DEFAULT= sun-jdk13
. endif
.endif
# Use one of the installed JVMs,...
#
.if !defined(_PKG_JVM)
. for _jvm_ in ${_PKG_JVMS_ACCEPTED}
. if !empty(_PKG_JVM_INSTALLED.${_jvm_}:M[yY][eE][sS])
_PKG_JVM?= ${_jvm_}
. else
_PKG_JVM_FIRSTACCEPTED?= ${_jvm_}
. endif
. endfor
#
# ...otherwise, prefer the default one if it's accepted,...
#
. if defined(_PKG_JVM_OK.${_PKG_JVM_DEFAULT}) && \
!empty(_PKG_JVM_OK.${_PKG_JVM_DEFAULT}:M[yY][eE][sS])
_PKG_JVM= ${_PKG_JVM_DEFAULT}
. endif
.endif
#
# ...otherwise, just use the first accepted JVM.
#
.if !defined(_PKG_JVM)
Fix typo (missing leading underscore), and add a currently unreachable section that errors out if there is no acceptable JVM found.
2002-10-14 09:25:04 +02:00
. if defined(_PKG_JVM_FIRSTACCEPTED)
_PKG_JVM= ${_PKG_JVM_FIRSTACCEPTED}
. endif
.endif
#
# If there are no acceptable JVMs, then generate an error.
#
.if !defined(_PKG_JVM)
# force an error
Make bulk builds mark packages failing due to "no acceptable JVM found" as unavailable instead of broken.
2004-12-14 01:08:57 +01:00
PKG_SKIP_REASON= "no acceptable JVM found"
on systems where _PKG_JVM is not set, set PKG_FAIL_REASON and set _PKG_JVM to "none" to avoid makefile errors.
2003-02-06 11:17:38 +01:00
_PKG_JVM= "none"
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
.endif
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
BUILDLINK_API_DEPENDS.blackdown-jdk13?= blackdown-jdk13-[0-9]*
BUILDLINK_API_DEPENDS.blackdown-jre13?= blackdown-jre13-[0-9]*
BUILDLINK_API_DEPENDS.jdk?= jdk-[0-9]*
BUILDLINK_API_DEPENDS.jdk14?= jdk14-[0-9]*
BUILDLINK_API_DEPENDS.kaffe?= kaffe>=1.1.4
BUILDLINK_API_DEPENDS.sun-jdk13?= sun-jdk13-[0-9]*
BUILDLINK_API_DEPENDS.sun-jre13?= sun-jre13-[0-9]*
BUILDLINK_API_DEPENDS.sun-jdk14?= sun-jdk14-[0-9]*
BUILDLINK_API_DEPENDS.sun-jre14?= sun-jre14-[0-9]*
BUILDLINK_API_DEPENDS.sun-jdk15?= sun-jdk15-[0-9]*
BUILDLINK_API_DEPENDS.sun-jre15?= sun-jre15-[0-9]*
#BUILDLINK_API_DEPENDS.win32-jdk?= win32-jdk>=0.1
Revert 1.29. With 1.29, e.g. devel/jgrasp would report: ===> Checking for vulnerabilities in jgrasp-1.7.0 => Checksum OK for jgrasp170.zip. ===> Extracting for jgrasp-1.7.0 ===> Required package : NOT found ===> Verifying reinstall for ../../lang/sun-jre13 even if sun-jre13/sun-jdk13 were already installed.
2004-07-14 15:37:09 +02:00
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
_JRE.blackdown-jdk13= blackdown-jre13
Use a table-based lookup scheme to pair up JREs to JDKs.
2003-01-29 21:52:01 +01:00
_JRE.jdk= jdk
Allow PKG_JVM=jdk14 (once a buildlink file has been added to wip/jdk14)
2004-06-03 22:19:08 +02:00
_JRE.jdk14= jdk14
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
_JRE.kaffe= kaffe
Use a table-based lookup scheme to pair up JREs to JDKs.
2003-01-29 21:52:01 +01:00
_JRE.sun-jdk13= sun-jre13
_JRE.sun-jdk14= sun-jre14
Add and enable {jdk,jre}15
2004-10-01 01:50:33 +02:00
_JRE.sun-jdk15= sun-jre15
Disable win32-jdk for now. It doesn't play well with bulk builds yet.
2005-01-12 18:23:46 +01:00
#_JRE.win32-jdk= win32-jdk
Use a table-based lookup scheme to pair up JREs to JDKs.
2003-01-29 21:52:01 +01:00
Set _JAVA_BASE_CLASSES to classes.zip or wre.jar in java-vm.mk, then use in bsd.pkg.mk. We are now more wonka friendly.
2003-01-29 10:34:29 +01:00
_JAVA_BASE_CLASSES= classes.zip
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
.if ${_PKG_JVM} == "blackdown-jdk13"
_JDK_PKGSRCDIR= ../../lang/blackdown-jdk13
_JRE_PKGSRCDIR= ../../lang/blackdown-jre13
_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/blackdown-1.3.1
. if !empty(MACHINE_PLATFORM:MNetBSD-*-powerpc)
MAKE_ENV+= THREADS_FLAG="green"
CONFIGURE_ENV+= THREADS_FLAG="green"
SCRIPTS_ENV+= THREADS_FLAG="green"
. endif
.elif ${_PKG_JVM} == "jdk"
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
_JDK_PKGSRCDIR= ../../lang/jdk
Use a table-based lookup scheme to pair up JREs to JDKs.
2003-01-29 21:52:01 +01:00
_JRE_PKGSRCDIR= ${_JDK_PKGSRCDIR}
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/jdk-1.1.8
Allow PKG_JVM=jdk14 (once a buildlink file has been added to wip/jdk14)
2004-06-03 22:19:08 +02:00
.elif ${_PKG_JVM} == "jdk14"
_JDK_PKGSRCDIR= ../../wip/jdk14
_JRE_PKGSRCDIR= ${_JDK_PKGSRCDIR}
_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/jdk-1.4.2
Add win32-jdk. While here, sort the per-JVM metadata sections by JVM name.
2004-10-11 15:38:18 +02:00
.elif ${_PKG_JVM} == "kaffe"
_JDK_PKGSRCDIR= ../../lang/kaffe
_JRE_PKGSRCDIR= ${_JDK_PKGSRCDIR}
_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/kaffe
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
.elif ${_PKG_JVM} == "sun-jdk13"
_JDK_PKGSRCDIR= ../../lang/sun-jdk13
_JRE_PKGSRCDIR= ../../lang/sun-jre13
_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/sun-1.3.1
.elif ${_PKG_JVM} == "sun-jdk14"
_JDK_PKGSRCDIR= ../../lang/sun-jdk14
_JRE_PKGSRCDIR= ../../lang/sun-jre14
sun-jdk14 has moved to .../java/sun-1.4.
2003-01-29 20:35:41 +01:00
_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/sun-1.4
Add and enable {jdk,jre}15
2004-10-01 01:50:33 +02:00
.elif ${_PKG_JVM} == "sun-jdk15"
_JDK_PKGSRCDIR= ../../lang/sun-jdk15
_JRE_PKGSRCDIR= ../../lang/sun-jre15
_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/sun-1.5
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
UNLIMIT_RESOURCES+= datasize
Disable win32-jdk for now. It doesn't play well with bulk builds yet.
2005-01-12 18:23:46 +01:00
#.elif ${_PKG_JVM} == "win32-jdk"
#_JDK_PKGSRCDIR= ../../lang/win32-jdk
#_JRE_PKGSRCDIR= ${_JDK_PKGSRCDIR}
#_JAVA_HOME_DEFAULT= ${LOCALBASE}/java/win32
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
.endif
Use "_JAVA_HOME_DEFAULT" if it is defined instead of using "EVAL_PREFIX". The later usually returns "${LOCALBASE}" which isn't useful for most of the packages providing a JVM.
2004-06-09 10:20:22 +02:00
.if defined(_JAVA_HOME_DEFAULT)
_JAVA_HOME= ${_JAVA_HOME_DEFAULT}
.else
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
EVAL_PREFIX+= _JAVA_HOME=${_JAVA_PKGBASE.${_PKG_JVM}}
Use "_JAVA_HOME_DEFAULT" if it is defined instead of using "EVAL_PREFIX". The later usually returns "${LOCALBASE}" which isn't useful for most of the packages providing a JVM.
2004-06-09 10:20:22 +02:00
.endif
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
# We always need a run-time dependency on the JRE.
make this also behave correctly when USE_BUILDLINK2 is not defined as well as _JRE_PKGSRCDIR not being defined
2003-02-07 00:44:07 +01:00
.if defined(_JRE_PKGSRCDIR)
USE_BUILDLINK3 is no longer optional (and cannot be turned off). Per mail to tech-pkg: ===== * USE_BUILDLINK3=YES will be unconditional. (In fact, USE_BUILDLINK3 will be ignored altogether by mk/; but see below.) * NO_BUILDLINK and NO_WRAPPER will be ignored by mk/. If a build happens, these phases will happen. * The existing NO_BUILD will imply the previous NO_BUILDLINK and NO_WRAPPER. If no build happens, those phases are not needed. * NO_TOOLS will be ignored by mk/. The tools phase, which provides much more than just the C compiler, will always happen regardless of package. This will make metapackage builds only slightly slower, in trade for far less user error.
2005-03-24 18:46:00 +01:00
. if exists(${_JRE_PKGSRCDIR}/buildlink3.mk)
. include "${_JRE_PKGSRCDIR}/buildlink3.mk"
Add buildlink3 bits.
2004-05-02 22:30:44 +02:00
. endif
make this also behave correctly when USE_BUILDLINK2 is not defined as well as _JRE_PKGSRCDIR not being defined
2003-02-07 00:44:07 +01:00
.endif
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
# If we are building Java software, then we need a build-time dependency on
# the JDK.
#
Allow for strangely-cased USE_JAVA values.
2002-12-31 15:39:59 +01:00
.if empty(USE_JAVA:M[rR][uU][nN])
Add buildlink3 bits.
2004-05-02 22:30:44 +02:00
. if defined(_JDK_PKGSRCDIR)
USE_BUILDLINK3 is no longer optional (and cannot be turned off). Per mail to tech-pkg: ===== * USE_BUILDLINK3=YES will be unconditional. (In fact, USE_BUILDLINK3 will be ignored altogether by mk/; but see below.) * NO_BUILDLINK and NO_WRAPPER will be ignored by mk/. If a build happens, these phases will happen. * The existing NO_BUILD will imply the previous NO_BUILDLINK and NO_WRAPPER. If no build happens, those phases are not needed. * NO_TOOLS will be ignored by mk/. The tools phase, which provides much more than just the C compiler, will always happen regardless of package. This will make metapackage builds only slightly slower, in trade for far less user error.
2005-03-24 18:46:00 +01:00
. if exists(${_JDK_PKGSRCDIR}/buildlink3.mk)
. include "${_JDK_PKGSRCDIR}/buildlink3.mk"
Add buildlink3 bits.
2004-05-02 22:30:44 +02:00
. endif
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
. endif
.endif
# PKG_JVM is a publicly readable variable containing the name of the JVM
# we will be using.
#
# PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME}
# for the PKG_JVM described above.
#
PKG_JVM:= ${_PKG_JVM}
.if defined(BUILDLINK_JAVA_PREFIX.${_PKG_JVM})
PKG_JAVA_HOME?= ${BUILDLINK_JAVA_PREFIX.${_PKG_JVM}}
.else
PKG_JAVA_HOME?= ${_JAVA_HOME}
.endif
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
.if !defined(CLASSPATH)
CLASSPATH_cmd= ${ECHO} `for p in \
${PKG_JAVA_HOME}/lib/${_JAVA_BASE_CLASSES} \
${PKG_JAVA_HOME}/lib/tools.jar; do \
${TEST} ! -f $$p || ${ECHO} $$p; done` \
. | ${TR} ' ' :
CLASSPATH?= ${CLASSPATH_cmd:sh}
.endif
Visual cleanup from tv-derecurse: Consolidate many MAKE_ENVs and SCRIPTS_ENVs into a common block. (CONFIGURE_ENVs to be done later.) Introduce new variable ALL_ENV which is automatically included into all of MAKE_ENV, SCRIPTS_ENV, and CONFIGURE_ENV; this allows much cleaner addition of the common CC/CXX/CFLAGS/etc. variables needed by all of these.
2005-02-11 17:36:49 +01:00
ALL_ENV+= CLASSPATH=${CLASSPATH:Q}
ALL_ENV+= JAVA_HOME=${PKG_JAVA_HOME}
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
BUILD_DEFS+= PKG_JVM PKG_JAVA_HOME
Applied all quoting fixes found by "pkglint --autofix".
2005-12-05 23:07:07 +01:00
MAKEFLAGS+= PKG_JVM=${PKG_JVM:Q}
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
PREPEND_PATH+= ${PKG_JAVA_HOME}/bin
Initial cut at java.mk that completely replaces the USE_JAVA-handling code in bsd.pkg.mk. The java.mk Java handling is largely based on the lang/python/pyversion.mk file. There are two new variables: PKG_JVM_DEFAULT is a user-settable variable whose value is the default JVM to use. PKG_JVMS_ACCEPTED is a package-settable list of JVMs that may be used as possible dependencies for the package. Two existing variables have been redefined to be only read-only, though there is some logic to handle legacy /etc/mk.conf which may contain an explicit PKG_JVM=... PKG_JVM is a publicly readable variable containing the name of the JVM we will be using. PKG_JAVA_HOME is a publicly readable variable containing ${JAVA_HOME} for the PKG_JVM described above. To do: Have some way to specify which JVMs are acceptable for each platform, and use the intersection of these JVMs and the ones listed in PKG_JVMS_ACCEPTED as the JVMS that may really be used. Currently, we assume all of the JVMs are usable by all platforms. I'm not sure if Darwin's special stub sun-{jre,jdk}13 packages are usable by buildlink2. This needs to be verified.
2002-10-13 11:29:12 +02:00
Move java.mk to java-vm.mk to avoid name conflict with devel/mk-files as suggested by Simon J. Gerraty.
2002-12-26 21:52:09 +01:00
.endif # JAVA_VM_MK
Reference in a new issue Copy permalink