kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/libmemmgr/Makefile

32 lines
936 B
Makefile
Raw Normal View History

Modernize the Makefile a bit. USE_TOOLS for groff, use SUBST instead of doing the equivalent thing by hand. This happens to unbreak the MirBSD build, where there is no groff installed by default.
2013-12-08 17:18:35 +01:00
# $NetBSD: Makefile,v 1.18 2013/12/08 16:18:35 bsiegert Exp $
Initial import of libmemmgr-1.04 into the packages collection. Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com) MemMgr is a fairly trivial memory management library. There is little it does that cannot be done using routines in the C library. (In fact, allocation and disposal is implemented using C library routines.) The purposes of MemMgr are two- fold. (i) Minimize configuration burden on applications that dynamically allocate memory. For instance, malloc() on some systems returns a char pointer; on others it returns a void pointer. The MemMgr library routines encapsulate system-specific configuration differences and exports a fixed interface which is system-indepen- dent. Once you compile and install it, you just use it without thinking about whether your UNIX is System V or BSD inspired. (ii) Provide two parallel sets of allocation routines which either return NULL (for applications which want to check) or panic (for applications which simply want to die) on allocation failures. Panicking is implemented using the ETM library, which introduces a dependency on the ETM distribution. So be it. I use ETM for all my programs anyway
2001-04-27 14:10:40 +02:00
#
DISTNAME= MemMgr-1.04
PKGNAME= libmemmgr-1.04
CATEGORIES= devel
Update MASTER_SITES and HOMEPAGE to www.snake.net.
2003-12-11 20:24:33 +01:00
MASTER_SITES= http://www.snake.net/software/MemMgr/
Initial import of libmemmgr-1.04 into the packages collection. Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com) MemMgr is a fairly trivial memory management library. There is little it does that cannot be done using routines in the C library. (In fact, allocation and disposal is implemented using C library routines.) The purposes of MemMgr are two- fold. (i) Minimize configuration burden on applications that dynamically allocate memory. For instance, malloc() on some systems returns a char pointer; on others it returns a void pointer. The MemMgr library routines encapsulate system-specific configuration differences and exports a fixed interface which is system-indepen- dent. Once you compile and install it, you just use it without thinking about whether your UNIX is System V or BSD inspired. (ii) Provide two parallel sets of allocation routines which either return NULL (for applications which want to check) or panic (for applications which simply want to die) on allocation failures. Panicking is implemented using the ETM library, which introduces a dependency on the ETM distribution. So be it. I use ETM for all my programs anyway
2001-04-27 14:10:40 +02:00
Reset maintainer, ben@ has resigned.
2006-12-15 15:34:18 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Update MASTER_SITES and HOMEPAGE to www.snake.net.
2003-12-11 20:24:33 +01:00
HOMEPAGE= ${MASTER_SITES}
COMMENT should start with a capital letter.
2003-07-21 18:35:12 +02:00
COMMENT= Simple memory manager library
Initial import of libmemmgr-1.04 into the packages collection. Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com) MemMgr is a fairly trivial memory management library. There is little it does that cannot be done using routines in the C library. (In fact, allocation and disposal is implemented using C library routines.) The purposes of MemMgr are two- fold. (i) Minimize configuration burden on applications that dynamically allocate memory. For instance, malloc() on some systems returns a char pointer; on others it returns a void pointer. The MemMgr library routines encapsulate system-specific configuration differences and exports a fixed interface which is system-indepen- dent. Once you compile and install it, you just use it without thinking about whether your UNIX is System V or BSD inspired. (ii) Provide two parallel sets of allocation routines which either return NULL (for applications which want to check) or panic (for applications which simply want to die) on allocation failures. Panicking is implemented using the ETM library, which introduces a dependency on the ETM distribution. So be it. I use ETM for all my programs anyway
2001-04-27 14:10:40 +02:00
Move WRKSRC definition away from the first paragraph in a Makefile.
2004-01-20 13:07:06 +01:00
WRKSRC= ${WRKDIR}/memmgr-1.04
Create directories before installing files into them.
2005-06-16 08:57:37 +02:00
INSTALLATION_DIRS= include lib
Modernize the Makefile a bit. USE_TOOLS for groff, use SUBST instead of doing the equivalent thing by hand. This happens to unbreak the MirBSD build, where there is no groff installed by default.
2013-12-08 17:18:35 +01:00
USE_TOOLS+= groff
Move WRKSRC definition away from the first paragraph in a Makefile.
2004-01-20 13:07:06 +01:00
Modernize the Makefile a bit. USE_TOOLS for groff, use SUBST instead of doing the equivalent thing by hand. This happens to unbreak the MirBSD build, where there is no groff installed by default.
2013-12-08 17:18:35 +01:00
SUBST_CLASSES+= prefix
SUBST_STAGE.prefix= post-patch
SUBST_MESSAGE.prefix= Fixing absolute paths.
SUBST_FILES.prefix= Makefile
SUBST_SED.prefix= -e 's|/usr/local|${PREFIX}|'
Initial import of libmemmgr-1.04 into the packages collection. Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com) MemMgr is a fairly trivial memory management library. There is little it does that cannot be done using routines in the C library. (In fact, allocation and disposal is implemented using C library routines.) The purposes of MemMgr are two- fold. (i) Minimize configuration burden on applications that dynamically allocate memory. For instance, malloc() on some systems returns a char pointer; on others it returns a void pointer. The MemMgr library routines encapsulate system-specific configuration differences and exports a fixed interface which is system-indepen- dent. Once you compile and install it, you just use it without thinking about whether your UNIX is System V or BSD inspired. (ii) Provide two parallel sets of allocation routines which either return NULL (for applications which want to check) or panic (for applications which simply want to die) on allocation failures. Panicking is implemented using the ETM library, which introduces a dependency on the ETM distribution. So be it. I use ETM for all my programs anyway
2001-04-27 14:10:40 +02:00
Change from using packaged install program and flags, to a do-install target in pkgsrc, in order to have a better chance of installing on Solaris and other platforms.
2003-12-13 17:20:09 +01:00
do-install:
Mechanical changes to add DESTDIR support to packages that install their files via a custom do-install target.
2008-03-03 18:45:33 +01:00
${INSTALL_DATA} ${WRKSRC}/libmemmgr.a ${DESTDIR}${PREFIX}/lib
${INSTALL_DATA} ${WRKSRC}/memmgr.h ${DESTDIR}${PREFIX}/include
${INSTALL_DATA_DIR} ${DESTDIR}${PREFIX}/share/doc/libmemmgr
Modernize the Makefile a bit. USE_TOOLS for groff, use SUBST instead of doing the equivalent thing by hand. This happens to unbreak the MirBSD build, where there is no groff installed by default.
2013-12-08 17:18:35 +01:00
${TOOLS_PATH.groff} -Tascii -ms ${WRKSRC}/memmgr.ms \
Mechanical changes to add DESTDIR support to packages that install their files via a custom do-install target.
2008-03-03 18:45:33 +01:00
>${DESTDIR}${PREFIX}/share/doc/libmemmgr/memmgr.txt
Initial import of libmemmgr-1.04 into the packages collection. Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com) MemMgr is a fairly trivial memory management library. There is little it does that cannot be done using routines in the C library. (In fact, allocation and disposal is implemented using C library routines.) The purposes of MemMgr are two- fold. (i) Minimize configuration burden on applications that dynamically allocate memory. For instance, malloc() on some systems returns a char pointer; on others it returns a void pointer. The MemMgr library routines encapsulate system-specific configuration differences and exports a fixed interface which is system-indepen- dent. Once you compile and install it, you just use it without thinking about whether your UNIX is System V or BSD inspired. (ii) Provide two parallel sets of allocation routines which either return NULL (for applications which want to check) or panic (for applications which simply want to die) on allocation failures. Panicking is implemented using the ETM library, which introduces a dependency on the ETM distribution. So be it. I use ETM for all my programs anyway
2001-04-27 14:10:40 +02:00
Convert to bl3, untested.
2005-04-05 13:11:05 +02:00
.include "../../devel/libetm/buildlink3.mk"
Initial import of libmemmgr-1.04 into the packages collection. Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com) MemMgr is a fairly trivial memory management library. There is little it does that cannot be done using routines in the C library. (In fact, allocation and disposal is implemented using C library routines.) The purposes of MemMgr are two- fold. (i) Minimize configuration burden on applications that dynamically allocate memory. For instance, malloc() on some systems returns a char pointer; on others it returns a void pointer. The MemMgr library routines encapsulate system-specific configuration differences and exports a fixed interface which is system-indepen- dent. Once you compile and install it, you just use it without thinking about whether your UNIX is System V or BSD inspired. (ii) Provide two parallel sets of allocation routines which either return NULL (for applications which want to check) or panic (for applications which simply want to die) on allocation failures. Panicking is implemented using the ETM library, which introduces a dependency on the ETM distribution. So be it. I use ETM for all my programs anyway
2001-04-27 14:10:40 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink