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

30 lines
873 B
Makefile
Raw Normal View History

Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
# $NetBSD: buildlink3.mk,v 1.18 2009/03/20 19:24:49 joerg Exp $
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
Replace mk/bsd.prefs.mk includes with bsd.fast.prefs.mk includes. The redundant parsing of bsd.prefs.mk is mostly avoided now and parse time e.g. for x11/kdebase3 gets reduced by up to 10%.
2006-12-12 22:52:34 +01:00
.include "../../mk/bsd.fast.prefs.mk"
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= gcc3-java
bsd.compiler.mk no longer adds dependencies or includes buildlink*.mk files if it's being included by bsd.prefs.mk, so we can safely move the BUILDLINK_DEPENDS line to its usual location.
2004-02-05 04:45:13 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
.if !defined(GCC3_JAVA_BUILDLINK3_MK)
GCC3_JAVA_BUILDLINK3_MK:=
Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-03-05 20:25:06 +01:00
Check if a variable is defined before checking its value.
2004-02-13 01:27:28 +01:00
. if defined(GCC3_INSTALLTO_SUBPREFIX)
. if ${GCC3_INSTALLTO_SUBPREFIX} != "gcc3"
Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-03-05 20:25:06 +01:00
GCC3_PKGMODIF= _${GCC3_INSTALLTO_SUBPREFIX}
Check if a variable is defined before checking its value.
2004-02-13 01:27:28 +01:00
. endif
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
. endif
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
BUILDLINK_API_DEPENDS.gcc3-java+= gcc3${GCC3_PKGMODIF}-java>=${_GCC_REQD}
BUILDLINK_ABI_DEPENDS.gcc3-java?= gcc3-java>=3.3.5nb1
Rename the internal package variable referred to by buildlink[23]. No functional change.
2004-03-18 05:19:39 +01:00
BUILDLINK_PKGSRCDIR.gcc3-java?= ../../lang/gcc3-java
BUILDLINK_LIBDIRS.gcc3-java?= \
lib ${_GCC_ARCHDIR:S/^${BUILDLINK_PREFIX.gcc3-java}\///}
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
# Packages that link against shared libraries need a full dependency.
Now that no package uses USE_GCC_SHLIB any longer, remove support for it from compiler.mk. Move the variable of the same name used by compiler/gcc.mk and the gcc* buildlink3 files into private namespace (_USE_GCC_SHLIB).
2004-11-22 23:24:46 +01:00
. if defined(_USE_GCC_SHLIB)
Rename the internal package variable referred to by buildlink[23]. No functional change.
2004-03-18 05:19:39 +01:00
BUILDLINK_DEPMETHOD.gcc3-java+= full
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
. else
Rename the internal package variable referred to by buildlink[23]. No functional change.
2004-03-18 05:19:39 +01:00
BUILDLINK_DEPMETHOD.gcc3-java?= build
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
. endif
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
.endif # GCC3_JAVA_BUILDLINK3_MK
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= -gcc3-java
Reference in a new issue Copy permalink