1
0
mirror of https://git.FreeBSD.org/ports.git synced 2024-12-14 03:10:47 +00:00
freebsd-ports/Mk/bsd.java.mk

537 lines
20 KiB
Makefile
Raw Normal View History

#-*- mode: Fundamental; tab-width: 4; -*-
# ex:ts=4
#
# bsd.java.mk - Support for Java-based ports.
#
# Created by: Ernst de Haan <znerd@FreeBSD.org>
#
# For FreeBSD committers:
# Please send all suggested changes to the maintainer instead of committing
# them to CVS yourself.
#
# $FreeBSD$
#
.if !defined(Java_Include)
Java_Include= bsd.java.mk
Java_Include_MAINTAINER= glewis@FreeBSD.org hq@FreeBSD.org
#-------------------------------------------------------------------------------
# Variables that each port can define:
#
# USE_JAVA Should be defined to the remaining variables to have any
# effect
#
# JAVA_VERSION List of space-separated suitable java versions for the
# port. An optional "+" allows you to specify a range of
# versions. (allowed values: 1.3[+] 1.4[+] 1.5[+] 1.6[+])
#
# JAVA_OS List of space-separated suitable JDK port operating systems
# for the port. (allowed values: native linux)
#
# JAVA_VENDOR List of space-separated suitable JDK port vendors for the
# port. (allowed values: freebsd bsdjava sun blackdown)
#
# JAVA_BUILD When set, it means that the selected JDK port should be
# added to build dependencies for the port.
#
# JAVA_RUN This variable works exactly the same as JAVA_BUILD but
# regarding run dependencies.
#
# USE_JIKES Whether the port should or should not use jikes(1) to build.
# See Stage 6 header for further detail.
#
# USE_ANT Should be defined when the port uses Apache Ant. Ant is thus
# considered to be the sub-make command. When no 'do-build'
# target is defined by the port, a default one will be set
# that simply runs Ant according to MAKE_ENV, MAKE_ARGS and
# ALL_TARGET. Read the documentation in bsd.port.mk for more
# information.
#
#-------------------------------------------------------------------------------
# Variables defined for the port:
#
# JAVA_PORT The name of the JDK port. (e.g. 'java/jdk14')
#
# JAVA_PORT_VERSION The version of the JDK port. (e.g. '1.4')
#
# JAVA_PORT_OS The operating system used by the JDK port. (e.g. 'linux')
#
# JAVA_PORT_VENDOR The vendor of the JDK port. (e.g. 'sun')
#
# JAVA_PORT_OS_DESCRIPTION Description of the operating system used by the
# JDK port. (e.g. 'Linux')
#
# JAVA_PORT_VENDOR_DESCRIPTION Description of the vendor of the JDK port.
# (e.g. 'FreeBSD Foundation')
#
# JAVA_HOME Path to the installation directory of the JDK. (e.g.
# '/usr/local/jdk1.3.1')
#
# JAVAC Path to the Java compiler to use. (e.g.
# '/usr/local/jdk1.5.0/bin/javac' or '/usr/local/bin/jikes')
#
# JAR Path to the JAR tool to use. (e.g.
# '/usr/local/jdk1.5.0/bin/jar' or '/usr/local/bin/fastjar')
#
# APPLETVIEWER Path to the appletviewer utility. (e.g.
# '/usr/local/linux-jdk1.3.1/bin/appletviewer')
#
# JAVA Path to the java executable. Use this for executing Java
# programs. (e.g. '/usr/local/jdk1.3.1/bin/java')
#
# JAVADOC Path to the javadoc utility program.
#
# JAVAH Path to the javah program.
#
# JAVAP Path to the javap program.
#
# JAVA_KEYTOOL Path to the keytool utility program.
#
# JAVA_N2A Path to the native2ascii tool.
#
# JAVA_POLICYTOOL Path to the policytool program.
#
# JAVA_SERIALVER Path to the serialver utility program.
#
# RMIC Path to the RMI stub/skeleton generator, rmic.
#
# RMIREGISTRY Path to the RMI registry program, rmiregistry.
#
# RMID Path to the RMI daemon program.
#
# JAVA_CLASSES Path to the archive that contains the JDK class files. On
# most JDKs, this is ${JAVA_HOME}/jre/lib/rt.jar.
#
# JAVASHAREDIR The base directory for all shared Java resources.
#
# JAVAJARDIR The directory where a port should install JAR files.
#
# JAVALIBDIR The directory where JAR files installed by other ports
# are located.
#
# HAVE_JIKES Defined and set to "yes" whenever the port will effectively
# use Jikes. See stage 6 header for further detail.
#
#-------------------------------------------------------------------------------
# Porter's hints
#
# To retrieve the Major version number from JAVA_PORT_VERSION (e.g. "1.3"):
# -> ${JAVA_PORT_VERSION:C/^([0-9])\.([0-9])(.*)$/\1.\2/}
#
#-------------------------------------------------------------------------------
# There are the following stages:
#
# Stage 1: Define constants
# Stage 2: Determine which JDK ports are installed and which JDK ports are
# suitable
# Stage 3: Decide the exact JDK to use (or install)
# Stage 4: Add any dependencies if necessary
# Stage 5: Define all settings for the port to use
#
. if defined(USE_JAVA)
#-------------------------------------------------------------------------------
# Stage 1: Define constants
#
# System-global directories
# NB: If the value of JAVALIBDIR is altered here it must also be altered
# in java/javavmwrapper/Makefile.
JAVASHAREDIR?= ${PREFIX}/share/java
JAVAJARDIR?= ${JAVASHAREDIR}/classes
JAVALIBDIR?= ${LOCALBASE}/share/java/classes
# Add appropriate substitutions to PLIST_SUB and LIST_SUB
PLIST_SUB+= JAVASHAREDIR="${JAVASHAREDIR:S,^${PREFIX}/,,}" \
JAVAJARDIR="${JAVAJARDIR:S,^${PREFIX}/,,}"
SUB_LIST+= JAVASHAREDIR="${JAVASHAREDIR}" \
JAVAJARDIR="${JAVAJARDIR}" \
JAVALIBDIR="${JAVALIBDIR}"
. if defined(JAVA_VERSION)
SUB_LIST+= JAVA_VERSION="${JAVA_VERSION}"
. endif
. if defined(JAVA_VENDOR)
SUB_LIST+= JAVA_VENDOR="${JAVA_VENDOR}"
. endif
. if defined(JAVA_OS)
SUB_LIST+= JAVA_OS="${JAVA_OS}"
. endif
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
# The complete list of Java versions, os and vendors supported.
__JAVA_VERSION_LIST= 1.3 1.4 1.5 1.6
_JAVA_VERSION_LIST= ${__JAVA_VERSION_LIST} ${__JAVA_VERSION_LIST:S/$/+/} 1.1+ 1.2+
_JAVA_OS_LIST= native linux
_JAVA_VENDOR_LIST= freebsd bsdjava sun blackdown
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
# Set all meta-information about JDK ports:
# port location, corresponding JAVA_HOME, JDK version, OS, vendor
_JAVA_PORT_NATIVE_FREEBSD_JDK_1_6_INFO= PORT=java/diablo-jdk16 HOME=${LOCALBASE}/diablo-jdk1.6.0 \
VERSION=1.6.0 OS=native VENDOR=freebsd
_JAVA_PORT_NATIVE_FREEBSD_JDK_1_5_INFO= PORT=java/diablo-jdk15 HOME=${LOCALBASE}/diablo-jdk1.5.0 \
VERSION=1.5.0 OS=native VENDOR=freebsd
_JAVA_PORT_NATIVE_BSDJAVA_JDK_1_3_INFO= PORT=java/jdk13 HOME=${LOCALBASE}/jdk1.3.1 \
VERSION=1.3.1 OS=native VENDOR=bsdjava
_JAVA_PORT_NATIVE_BSDJAVA_JDK_1_4_INFO= PORT=java/jdk14 HOME=${LOCALBASE}/jdk1.4.2 \
VERSION=1.4.2 OS=native VENDOR=bsdjava
2005-01-20 08:43:09 +00:00
_JAVA_PORT_NATIVE_BSDJAVA_JDK_1_5_INFO= PORT=java/jdk15 HOME=${LOCALBASE}/jdk1.5.0 \
VERSION=1.5.0 OS=native VENDOR=bsdjava
_JAVA_PORT_NATIVE_BSDJAVA_JDK_1_6_INFO= PORT=java/jdk16 HOME=${LOCALBASE}/jdk1.6.0 \
VERSION=1.6.0 OS=native VENDOR=bsdjava
_JAVA_PORT_LINUX_BLACKDOWN_JDK_1_4_INFO= PORT=java/linux-blackdown-jdk14 HOME=${LOCALBASE}/linux-blackdown-jdk1.4.2 \
VERSION=1.4.2 OS=linux VENDOR=blackdown
_JAVA_PORT_LINUX_SUN_JDK_1_3_INFO= PORT=java/linux-sun-jdk13 HOME=${LOCALBASE}/linux-sun-jdk1.3.1 \
VERSION=1.3.1 OS=linux VENDOR=sun
_JAVA_PORT_LINUX_SUN_JDK_1_4_INFO= PORT=java/linux-sun-jdk14 HOME=${LOCALBASE}/linux-sun-jdk1.4.2 \
VERSION=1.4.2 OS=linux VENDOR=sun
_JAVA_PORT_LINUX_SUN_JDK_1_5_INFO= PORT=java/linux-sun-jdk15 HOME=${LOCALBASE}/linux-sun-jdk1.5.0 \
VERSION=1.5.0 OS=linux VENDOR=sun
_JAVA_PORT_LINUX_SUN_JDK_1_6_INFO= PORT=java/linux-sun-jdk16 HOME=${LOCALBASE}/linux-sun-jdk1.6.0 \
VERSION=1.6.0 OS=linux VENDOR=sun
# Verbose description for each VENDOR
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
_JAVA_VENDOR_freebsd= "FreeBSD Foundation"
_JAVA_VENDOR_bsdjava= "BSD Java Porting Team"
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
_JAVA_VENDOR_blackdown= Blackdown
_JAVA_VENDOR_sun= Sun
# Verbose description for each OS
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
_JAVA_OS_native= Native
_JAVA_OS_linux= Linux
# Enforce preferred Java ports according to OS
. if (${OSVERSION} >= 600000 && ${OSVERSION} < 800000)
_JAVA_PREFERRED_PORTS+= JAVA_PORT_NATIVE_FREEBSD_JDK_1_6
. else
_JAVA_PREFERRED_PORTS+= JAVA_PORT_NATIVE_BSDJAVA_JDK_1_6
. endif
# List all JDK ports
__JAVA_PORTS_ALL= JAVA_PORT_NATIVE_FREEBSD_JDK_1_6 \
JAVA_PORT_NATIVE_FREEBSD_JDK_1_5 \
JAVA_PORT_NATIVE_BSDJAVA_JDK_1_6 \
JAVA_PORT_NATIVE_BSDJAVA_JDK_1_5 \
2005-01-20 08:43:09 +00:00
JAVA_PORT_NATIVE_BSDJAVA_JDK_1_4 \
JAVA_PORT_NATIVE_BSDJAVA_JDK_1_3 \
JAVA_PORT_LINUX_SUN_JDK_1_6 \
JAVA_PORT_LINUX_SUN_JDK_1_5 \
JAVA_PORT_LINUX_SUN_JDK_1_4 \
JAVA_PORT_LINUX_SUN_JDK_1_3 \
JAVA_PORT_LINUX_BLACKDOWN_JDK_1_4
_JAVA_PORTS_ALL= ${JAVA_PREFERRED_PORTS} \
${_JAVA_PREFERRED_PORTS} \
${__JAVA_PORTS_ALL}
# Set the name of the file that indicates that a JDK is indeed installed, as a
# relative path within the JAVA_HOME directory.
_JDK_FILE=bin/javac
# Set the path to Jikes and define the Jikes dependency
_JIKES_PATH= ${LOCALBASE}/bin/jikes
DEPEND_JIKES= ${_JIKES_PATH}:${PORTSDIR}/java/jikes
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
#-------------------------------------------------------------------------------
# Stage 2: Determine which JDK ports are suitable and which JDK ports are
# suitable
#
# From here, the port is using bsd.java.mk v2.0
# Error checking: defined JAVA_{HOME,PORT,PORT_VERSION,PORT_VENDOR,PORT_OS}
. for variable in JAVA_HOME JAVA_PORT JAVA_PORT_VERSION JAVA_PORT_VENDOR JAVA_PORT_OS
. if defined(${variable})
check-makevars::
@${ECHO_CMD} "${PKGNAME}: Environment error: \"${variable}\" should not be defined."
@${FALSE}
. endif
. endfor
# Error checking: JAVA_VERSION
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.if !defined(_JAVA_VERSION_LIST_REGEXP)
_JAVA_VERSION_LIST_REGEXP!= ${ECHO_CMD} "${_JAVA_VERSION_LIST}" | ${SED} "s/ /\\\|/g"
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.endif
check-makevars::
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
@test ! -z "${JAVA_VERSION}" && ( ${ECHO_CMD} "${JAVA_VERSION}" | ${TR} " " "\n" | ${GREP} -q "${_JAVA_VERSION_LIST_REGEXP}" || \
(${ECHO_CMD} "${PKGNAME}: Makefile error: \"${JAVA_VERSION}\" is not a valid value for JAVA_VERSION. It should be one or more of: ${__JAVA_VERSION_LIST} (with an optional \"+\" suffix.)"; ${FALSE})) || true
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
# Error checking: JAVA_VENDOR
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.if !defined(_JAVA_VENDOR_LIST_REGEXP)
_JAVA_VENDOR_LIST_REGEXP!= ${ECHO_CMD} "${_JAVA_VENDOR_LIST}" | ${SED} "s/ /\\\|/g"
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.endif
check-makevars::
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
@test ! -z "${JAVA_VENDOR}" && ( ${ECHO_CMD} "${JAVA_VENDOR}" | ${TR} " " "\n" | ${GREP} -q "${_JAVA_VENDOR_LIST_REGEXP}" || \
(${ECHO_CMD} "${PKGNAME}: Makefile error: \"${JAVA_VENDOR}\" is not a valid value for JAVA_VENDOR. It should be one or more of: ${_JAVA_VENDOR_LIST}"; \
${FALSE})) || true
# Error checking: JAVA_OS
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.if !defined(_JAVA_OS_LIST_REGEXP)
_JAVA_OS_LIST_REGEXP!= ${ECHO_CMD} "${_JAVA_OS_LIST}" | ${SED} "s/ /\\\|/g"
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.endif
check-makevars::
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
@test ! -z "${JAVA_OS}" && ( ${ECHO_CMD} "${JAVA_OS}" | ${TR} " " "\n" | ${GREP} -q "${_JAVA_OS_LIST_REGEXP}" || \
(${ECHO_CMD} "${PKGNAME}: Makefile error: \"${JAVA_OS}\" is not a valid value for JAVA_OS. It should be one or more of: ${_JAVA_OS_LIST}"; \
${FALSE})) || true
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
# Set default values for JAVA_BUILD and JAVA_RUN
# When nothing is set, assume JAVA_BUILD=jdk and JAVA_RUN=jre
# (unless NO_BUILD is set)
. if !defined(JAVA_EXTRACT) && !defined(JAVA_BUILD) && !defined(JAVA_RUN)
. if !defined(NO_BUILD)
JAVA_BUILD= jdk
. endif
JAVA_RUN= jre
. endif
# JDK dependency setting
. undef _JAVA_PORTS_INSTALLED
. undef _JAVA_PORTS_POSSIBLE
. if defined(JAVA_VERSION)
_JAVA_VERSION= ${JAVA_VERSION:S/1.1+/1.3+/:S/1.2+/1.3+/:S/1.3+/1.3 1.4+/:S/1.4+/1.4 1.5+/:S/1.5+/1.5 1.6+/:S/1.6+/1.6/}
. else
_JAVA_VERSION= ${__JAVA_VERSION_LIST}
. endif
. if defined(JAVA_OS)
_JAVA_OS= ${JAVA_OS}
. else
_JAVA_OS= ${_JAVA_OS_LIST}
. endif
. if defined(JAVA_VENDOR)
_JAVA_VENDOR= ${JAVA_VENDOR}
. else
_JAVA_VENDOR= ${_JAVA_VENDOR_LIST}
. endif
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
. for A_JAVA_PORT in ${_JAVA_PORTS_ALL}
A_JAVA_PORT_INFO:= ${A_JAVA_PORT:S/^/\${_/:S/$/_INFO}/}
A_JAVA_PORT_HOME= ${A_JAVA_PORT_INFO:MHOME=*:S,HOME=,,}
A_JAVA_PORT_VERSION= ${A_JAVA_PORT_INFO:MVERSION=*:C/VERSION=([0-9])\.([0-9])(.*)/\1.\2/}
A_JAVA_PORT_OS= ${A_JAVA_PORT_INFO:MOS=*:S,OS=,,}
A_JAVA_PORT_VENDOR= ${A_JAVA_PORT_INFO:MVENDOR=*:S,VENDOR=,,}
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.if !defined(_JAVA_PORTS_INSTALLED)
A_JAVA_PORT_INSTALLED!= ${TEST} -x "${A_JAVA_PORT_HOME}/${_JDK_FILE}" \
&& ${ECHO_CMD} "${A_JAVA_PORT}" \
|| ${TRUE}
__JAVA_PORTS_INSTALLED!= ${ECHO_CMD} "${__JAVA_PORTS_INSTALLED} ${A_JAVA_PORT_INSTALLED}"
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.endif
# The magic here is that we want to test for a substring using only shell builtins (to avoid forking)
# Our shell does not have an explicit substring operator, but we can build one by using the '#'
# deletion operator ('%' would also work). We try to delete the pattern "*${substr}*" and compare it
# to the original string. If they differ, the substring matched.
#
# We can't do this in make because it doesn't allow nested modifiers ${foo:${bar}}
#
A_JAVA_PORT_POSSIBLE!= ver="${_JAVA_VERSION}"; os="${_JAVA_OS}"; vendor="${_JAVA_VENDOR}"; \
${TEST} "$${ver\#*${A_JAVA_PORT_VERSION}*}" != "${_JAVA_VERSION}" -a \
"$${os\#*${A_JAVA_PORT_OS}*}" != "${_JAVA_OS}" -a \
"$${vendor\#*${A_JAVA_PORT_VENDOR}*}" != "${_JAVA_VENDOR}" && \
${ECHO_CMD} "${A_JAVA_PORT}" || ${TRUE}
__JAVA_PORTS_POSSIBLE:= ${__JAVA_PORTS_POSSIBLE} ${A_JAVA_PORT_POSSIBLE}
. endfor
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.if !defined(_JAVA_PORTS_INSTALLED)
_JAVA_PORTS_INSTALLED= ${__JAVA_PORTS_INSTALLED:C/ [ ]+/ /g}
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
.endif
_JAVA_PORTS_POSSIBLE= ${__JAVA_PORTS_POSSIBLE:C/ [ ]+/ /g}
#-------------------------------------------------------------------------------
# Stage 3: Decide the exact JDK to use (or install)
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
#
# Find an installed JDK port that matches the requirements of the port
. undef _JAVA_PORTS_INSTALLED_POSSIBLE
. for A_JAVA_PORT in ${_JAVA_PORTS_POSSIBLE}
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
A_JAVA_PORT_INSTALLED_POSSIBLE!= inst="${_JAVA_PORTS_INSTALLED}"; \
${TEST} "$${inst\#*${A_JAVA_PORT}*}" != "${_JAVA_PORTS_INSTALLED}" && \
${ECHO_CMD} "${A_JAVA_PORT}" || ${TRUE}
__JAVA_PORTS_INSTALLED_POSSIBLE:= ${__JAVA_PORTS_INSTALLED_POSSIBLE} ${A_JAVA_PORT_INSTALLED_POSSIBLE}
. endfor
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
_JAVA_PORTS_INSTALLED_POSSIBLE= ${__JAVA_PORTS_INSTALLED_POSSIBLE:C/[ ]+//g}
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
. if ${_JAVA_PORTS_INSTALLED_POSSIBLE} != ""
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
. for i in ${_JAVA_PORTS_INSTALLED_POSSIBLE}
. if !defined(_JAVA_PORTS_INSTALLED_POSSIBLE_shortcircuit)
_JAVA_PORT= $i
_JAVA_PORTS_INSTALLED_POSSIBLE_shortcircuit= 1
. endif
. endfor
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
# If no installed JDK port fits, then pick one from the list of possible ones
. else
Major optimizations for 'make index' and other recursive traversal targets. * Use /rescue/sh for index builds instead of /bin/sh, when it exists. The former is statically linked and faster to execute, which becomes significant when executing it tens of thousands of times. This trick can be used with other recursive targets by passing in __MAKE_SHELL. * Get rid of make variable assignments that use != command invocations in the critical path, using several methods: - rewriting logic to use shell or make builtins instead of external command executions - macroizing commands and executing them in the targets where they are needed instead of with every invocation of make - precomputing the results of invariant commands in bsd.port.subdir.mk and passing them in explicitly to child makes, and using this to avoid recalculation in all the children. NB: the commands are still run one per top-level subdirectory but this does not currently seem to be a major issue. They could be moved further up into the top-level Makefile at the cost of some cleanliness. - Committers are strongly discouraged from adding further "bare" != assignments to the ports tree, even in their own ports. One of the above strategies should be used to avoid future bloat. * Rewrite the core 'describe' target to work entirely within a single shell process using only builtin commands. The old version is retained as a backup for use on systems older than 603104, which does not have the make :u modifier. This cuts down the number of processes executed during the course of a 'make index' by an order of magnitude, and we are essentially now amortized to the minimum of a single make + sh instance per port, plus whatever commands the port makefile itself executes (which are usually unnecessary and bogus). * Less validation of the WWW: target is performed; this can become policed at a port level by portlint. Specifically we look at the second word of the first line beginning with "WWW:" in pkg-descr, and append "http://" to it unless it already begins with "http://", "https://" or "ftp://". Thanks to dougb for the idea of how to extract WWW: using shell builtins. * Use the "true" shell builtin instead of echo > /dev/null for a measurable decrease in CPU use. * Add a note about dubious escaping strategy in bsd.port.subdir.mk * Minor change in output of 'make describe': it no longer strips trailing CR characters from pkg-descr files with MSDOS CR/LF termination. Instead the makeindex perl script that post-processes make describe into the INDEX is tweaked to strip on input. The bottom line is that on my test hardware INDEX builds are now faster by more than a factor of 2 and with a reduction in system time by a factor of 4-8 depending on configuration.
2008-07-19 17:59:41 +00:00
. for i in ${_JAVA_PORTS_POSSIBLE}
. if !defined(_JAVA_PORTS_POSSIBLE_shortcircuit)
_JAVA_PORT= $i
_JAVA_PORTS_POSSIBLE_shortcircuit= 1
. endif
. endfor
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
. endif
_JAVA_PORT_INFO:= ${_JAVA_PORT:S/^/\${_/:S/$/_INFO}/}
JAVA_PORT= ${_JAVA_PORT_INFO:MPORT=*:S,PORT=,,}
JAVA_HOME= ${_JAVA_PORT_INFO:MHOME=*:S,HOME=,,}
JAVA_PORT_VERSION= ${_JAVA_PORT_INFO:MVERSION=*:S,VERSION=,,}
JAVA_PORT_OS= ${_JAVA_PORT_INFO:MOS=*:S,OS=,,}
JAVA_PORT_VENDOR= ${_JAVA_PORT_INFO:MVENDOR=*:S,VENDOR=,,}
Bring in the new bsd.java.mk 2.0. bsd.java.mk now provides a new set of macros to be used by ports that require a JDK. When USE_JAVA is set, the following variables may be set in order to give to precision regarding the requirements of the port: - JAVA_VERSION: A list of space-separated suitable java versions for the port. An optional "+" allows you to specify a range of versions. (allowed values: 1.1[+] 1.2[+] 1.3[+] 1.4[+]) - JAVA_OS: A list of space-separated suitable JDK port operating systems for the port. (allowed values: native linux) - JAVA_VENDOR: A list of space-sperated suitable JDK port vendors for the port. (allowed values: freebsd bsdjava sun ibm blackdown) - JAVA_BUILD: When set, it means that the selected JDK port should be added to build dependencies for the port. - JAVA_RUN: This variable works exactly the same as JAVA_BUILD but regarding run dependencies. Here are some of the macros defined after setting USE_JAVA: - JAVA_PORT: The name of the JDK port (e.g. java/jdk14) - JAVA_HOME: The home of the JDK port in the local base - JAVA_PORT_VERSION: The version of the JDK port. - JAVA_PORT_OS: The operating system used by the JDK port. - JAVA_PORT_VENDOR: The vendor of the JDK port. - And many macros for the commonly used java executables, such as JAVA, JAVAC, JAVADOC, JAVAH, RMID, JAR... bsd.java.mk 2.0 is backward compatible with the previous version. Using the new features is strongly encouraged, since the old bsd.java.mk 1.0 features will be deprecated and removed in the near future. You will find more detailed info (as well as a quick tutorial) at: http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html If you experience any problems with java based ports that you believe is due to this change then please let me know. PR: 63511 Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
2004-04-03 03:37:05 +00:00
JAVA_PORT_VENDOR_DESCRIPTION:= ${JAVA_PORT_VENDOR:S/^/\${_JAVA_VENDOR_/:S/$/}/}
JAVA_PORT_OS_DESCRIPTION:= ${JAVA_PORT_OS:S/^/\${_JAVA_OS_/:S/$/}/}
#-------------------------------------------------------------------------------
# Stage 4: Add any dependencies if necessary
#
# Jikes support: If USE_JIKES is set to YES, then use Jikes. If USE_JIKES is
# set to NO, then don't use it. If it is set to a different value, then fail
# with an error message. Otherwise USE_JIKES is not set, in which case it is
# checked if Jikes is already installed. If it is, then it will be used,
# otherwise it will not be used.
#
# As a result, HAVE_JIKES is defined and set to "yes" when Jikes is used by the
# port according to the above policy.
. undef HAVE_JIKES
# Enforce USE_JIKES=NO if not defined and using Java 1.5+
# XXX: This is a temporary fix to be removed when Jikes supports Java 1.5
. if (${JAVA_PORT_VERSION:C/^([0-9])\.([0-9])(.*)$/\1.\2/} == "1.5") || \
(${JAVA_PORT_VERSION:C/^([0-9])\.([0-9])(.*)$/\1.\2/} == "1.6")
USE_JIKES?= NO
. endif
# First test if USE_JIKES has a valid value
. if defined(USE_JIKES) && !(${USE_JIKES:U} == "YES") && !(${USE_JIKES:U} == "NO")
check-makevars::
@${ECHO_CMD} "${PKGNAME}: Makefile error: \"${USE_JIKES}\" is not a valid value for USE_JIKES. It should be YES or NO, or it should be undefined.";
@${FALSE}
. endif
# Then test if jikes is needed or available: -> HAVE_JIKES=yes
. if (exists(${_JIKES_PATH}) && (!defined(USE_JIKES) || (${USE_JIKES:U} == "YES"))) \
|| (defined(USE_JIKES) && (${USE_JIKES:U} == "YES"))
HAVE_JIKES= yes
. endif
# Add jikes port to the dependencies if needed
. if !defined(NO_BUILD) && defined(HAVE_JIKES)
BUILD_DEPENDS+= ${DEPEND_JIKES}
. endif
# Ant Support: USE_ANT --> JAVA_BUILD=jdk
. if defined(USE_ANT)
JAVA_BUILD= jdk
. endif
# Add the JDK port to the dependencies
DEPEND_JAVA= ${JAVA}:${PORTSDIR}/${JAVA_PORT}
. if defined(JAVA_EXTRACT)
EXTRACT_DEPENDS+= ${DEPEND_JAVA}
. endif
. if defined(JAVA_BUILD)
. if defined(NO_BUILD)
check-makevars::
@${ECHO_CMD} "${PKGNAME}: Makefile error: JAVA_BUILD and NO_BUILD cannot be set at the same time.";
@${FALSE}
. endif
BUILD_DEPENDS+= ${DEPEND_JAVA}
. endif
. if defined(JAVA_RUN)
RUN_DEPENDS+= ${DEPEND_JAVA}
. endif
# Ant support: default do-build target
. if defined(USE_ANT)
ANT?= ${LOCALBASE}/bin/ant
MAKE_ENV+= JAVA_HOME=${JAVA_HOME}
. if defined(HAVE_JIKES)
MAKE_ARGS+= -Dbuild.compiler=jikes
. endif
BUILD_DEPENDS+= ${ANT}:${PORTSDIR}/devel/apache-ant
ALL_TARGET?=
. if !target(do-build)
do-build:
@(cd ${BUILD_WRKSRC}; \
${SETENV} ${MAKE_ENV} ${ANT} ${MAKE_ARGS} ${ALL_TARGET})
. endif
. endif
#-----------------------------------------------------------------------------
# Stage 5: Define all settings for the port to use
#
# At this stage both JAVA_HOME and JAVA_PORT are definitely given a value.
#
# Define the location of the Java compiler. If HAVE_JIKES is defined, then
# use Jikes.
# Only define JAVAC if a JDK is needed or USE_JIKES=yes
. undef JAVAC
# Then test if a JAVAC has to be set (JAVA_BUILD==jdk)
. if defined(JAVA_BUILD)
. if (${JAVA_BUILD:U} == "JDK") && !defined(JAVAC)
# Use jikes if available and not explicitly forbidden (see Stage 6)
. if defined(HAVE_JIKES)
JAVAC?= ${_JIKES_PATH} -bootclasspath ${JAVA_CLASSES}
# Otherwise use 'javac'
. else
JAVAC?= ${JAVA_HOME}/bin/javac
. endif
. endif
. endif
# Define the location of some more executables.
APPLETVIEWER?= ${JAVA_HOME}/bin/appletviewer
JAR?= ${JAVA_HOME}/bin/jar
JAVA?= ${JAVA_HOME}/bin/java
JAVADOC?= ${JAVA_HOME}/bin/javadoc
JAVAH?= ${JAVA_HOME}/bin/javah
JAVAP?= ${JAVA_HOME}/bin/javap
JAVA_N2A?= ${JAVA_HOME}/bin/native2ascii
JAVA_SERIALVER?=${JAVA_HOME}/bin/serialver
RMIC?= ${JAVA_HOME}/bin/rmic
RMIREGISTRY?= ${JAVA_HOME}/bin/rmiregistry
JAVA_KEYTOOL?= ${JAVA_HOME}/bin/keytool
JAVA_POLICYTOOL?= ${JAVA_HOME}/bin/policytool
RMID?= ${JAVA_HOME}/bin/rmid
# Set the location of the ZIP or JAR file with all standard Java classes.
JAVA_CLASSES= ${JAVA_HOME}/jre/lib/rt.jar
#-------------------------------------------------------------------------------
# Additional Java support
# Debug target
# Use it to check Java dependency while porting
java-debug:
@${ECHO_CMD} "# User specified parameters:"
@${ECHO_CMD} "JAVA_VERSION= ${JAVA_VERSION} (${_JAVA_VERSION})"
@${ECHO_CMD} "JAVA_OS= ${JAVA_OS} (${_JAVA_OS})"
@${ECHO_CMD} "JAVA_VENDOR= ${JAVA_VENDOR} (${_JAVA_VENDOR})"
@${ECHO_CMD} "JAVA_BUILD= ${JAVA_BUILD}"
@${ECHO_CMD} "JAVA_RUN= ${JAVA_RUN}"
@${ECHO_CMD} "JAVA_EXTRACT= ${JAVA_EXTRACT}"
@${ECHO_CMD}
@${ECHO_CMD} "# JDK port dependency selection process:"
@${ECHO_CMD} "_JAVA_PORTS_POSSIBLE= ${_JAVA_PORTS_POSSIBLE}"
@${ECHO_CMD} "_JAVA_PORTS_INSTALLED= ${_JAVA_PORTS_INSTALLED}"
@${ECHO_CMD} "_JAVA_PORTS_INSTALLED_POSSIBLE= ${_JAVA_PORTS_INSTALLED_POSSIBLE}"
@${ECHO_CMD} "_JAVA_PORT= ${_JAVA_PORT}"
@${ECHO_CMD} "_JAVA_PORT_INFO= ${_JAVA_PORT_INFO:S/\t/ /}"
@${ECHO_CMD}
@${ECHO_CMD} "# Selected JDK port:"
@${ECHO_CMD} "JAVA_PORT= ${JAVA_PORT}"
@${ECHO_CMD} "JAVA_HOME= ${JAVA_HOME}"
@${ECHO_CMD} "JAVA_PORT_VERSION= ${JAVA_PORT_VERSION}"
@${ECHO_CMD} "JAVA_PORT_OS= ${JAVA_PORT_OS} (${JAVA_PORT_OS_DESCRIPTION})"
@${ECHO_CMD} "JAVA_PORT_VENDOR= ${JAVA_PORT_VENDOR} (${JAVA_PORT_VENDOR_DESCRIPTION})"
@${ECHO_CMD}
@${ECHO_CMD} "# Additional variables:"
@${ECHO_CMD} "JAVAC= ${JAVAC}"
@${ECHO_CMD} "JAVA_CLASSES= ${JAVA_CLASSES}"
. endif
.endif