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

31 lines
857 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.3 2009/03/20 19:24:52 joerg Exp $
Here's python25-2.5.2, courtesy of pkgsrc-wip. It probably needs plenty more polishing, especially on !NetBSD. Python 2.4 will remain the default for some time. For the new features in Python 2.5, look here: * http://docs.python.org/whatsnew/whatsnew25.html
2008-04-24 03:50:55 +02: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+= python25
Here's python25-2.5.2, courtesy of pkgsrc-wip. It probably needs plenty more polishing, especially on !NetBSD. Python 2.4 will remain the default for some time. For the new features in Python 2.5, look here: * http://docs.python.org/whatsnew/whatsnew25.html
2008-04-24 03:50:55 +02: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(PYTHON25_BUILDLINK3_MK)
PYTHON25_BUILDLINK3_MK:=
Here's python25-2.5.2, courtesy of pkgsrc-wip. It probably needs plenty more polishing, especially on !NetBSD. Python 2.4 will remain the default for some time. For the new features in Python 2.5, look here: * http://docs.python.org/whatsnew/whatsnew25.html
2008-04-24 03:50:55 +02:00
BUILDLINK_API_DEPENDS.python25+= python25>=2.5
BUILDLINK_ABI_DEPENDS.python25+= python25>=2.5.2
BUILDLINK_PKGSRCDIR.python25?= ../../lang/python25
. if defined(BUILDLINK_DEPMETHOD.python)
BUILDLINK_DEPMETHOD.python25?= ${BUILDLINK_DEPMETHOD.python}
. endif
BUILDLINK_INCDIRS.python25+= include/python2.5
BUILDLINK_LIBDIRS.python25+= lib/python2.5/config
BUILDLINK_TRANSFORM+= l:python:python2.5
Any package that determines libraries to link via: $PYTHON -c "from distutils import sysconfig; print sysconfig.get_config_var('SHLIBS');" ... where bdb.buildlink.mk has been used and it satisfied the requirement from Pkgsrc (E.g. via databases/db4) would fail to build because the required -ldb4 library was not itself buildlinked. To rectify this, pull in bdb.buildlink.mk in python??/buildlink3.mk under the same conditions as it is pulled in in the package's own makefile. No revision bump required, this almost certainly only affects packages and environments that simply wouldn't build at all prior to the fix. Fixes the build of py-ORBit on Linux (Python 2.4 or 2.5), and PR39377.
2009-01-23 04:05:53 +01:00
.include "../../mk/bsd.fast.prefs.mk"
.if ${OPSYS} != "IRIX"
. include "../../mk/bdb.buildlink3.mk"
.endif
Here's python25-2.5.2, courtesy of pkgsrc-wip. It probably needs plenty more polishing, especially on !NetBSD. Python 2.4 will remain the default for some time. For the new features in Python 2.5, look here: * http://docs.python.org/whatsnew/whatsnew25.html
2008-04-24 03:50:55 +02:00
.include "../../mk/dlopen.buildlink3.mk"
.include "../../mk/pthread.buildlink3.mk"
.include "../../devel/gettext-lib/buildlink3.mk"
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 # PYTHON25_BUILDLINK3_MK
Here's python25-2.5.2, courtesy of pkgsrc-wip. It probably needs plenty more polishing, especially on !NetBSD. Python 2.4 will remain the default for some time. For the new features in Python 2.5, look here: * http://docs.python.org/whatsnew/whatsnew25.html
2008-04-24 03:50:55 +02: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+= -python25
Reference in a new issue Copy permalink