Commit graph

23 commits

Author SHA1 Message Date
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
wiz
5323e5f21b Update to 1.4.0.5: minor undocumented changes. 2005-03-29 14:28:05 +00:00
wiz
6e02d7ee41 Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs.
Suggested by Roland Illig, ok'd by various.
2004-12-03 15:14:50 +00:00
jlam
1a280185e1 Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:

	lib/libfoo.a
	lib/libfoo.la
	lib/libfoo.so
	lib/libfoo.so.0
	lib/libfoo.so.0.1

one simply needs:

	lib/libfoo.la

and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.

Also make LIBTOOLIZE_PLIST default to "yes".
2004-09-22 08:09:14 +00:00
wiz
caf13780db Unused. 2004-05-05 08:27:56 +00:00
jlam
326169077a USE_BUILDLINK3 must be set to "yes" or "no", not defined/undefined. 2004-03-23 04:40:59 +00:00
jlam
9ff0e10340 Reorder location and setting of BUILDLINK_PACKAGES to match template
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-03-05 19:25:06 +00:00
heinz
18a916d5e6 Use $FIND with "-print". Noted by Georg Schwarz in PR pkg/24248 2004-01-27 00:53:10 +00:00
jlam
a7d877ca6a Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. In
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files.  In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
2004-01-24 03:26:45 +00:00
jlam
02eb6f1e19 bl3ify 2004-01-05 20:38:34 +00:00
jlam
d279e6f535 Use S/+$// instead of C/\+$// to save a backslash. Very highly
recommended by seb :)
2004-01-05 11:05:44 +00:00
jlam
47bb2aae5f Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk. 2004-01-04 23:34:04 +00:00
jlam
339cd13cb2 Initial sprinkling of work-in-progress buildlink3.mk files for using the
buildlink3 framework.
2004-01-03 23:06:43 +00:00
grant
62732b9100 replace <malloc.h> with <stdlib.h>, allowing this to build on systems
without a working <malloc.h>, eg. FreeBSD 5.x.
2003-10-26 06:50:10 +00:00
jmmv
f1446ddf2b Drop trailing whitespace. Ok'ed by wiz. 2003-05-06 17:40:18 +00:00
jlam
eeb82239ac Correct the aalib-x11-config script to return "-laa-x11" instead of "-laa".
Bump the PKGREVISION since this is a user-visible change.
2002-10-31 08:17:24 +00:00
jlam
a36f1836ae Remove buildlink.mk files that aren't used by any other files in pkgsrc. 2002-08-28 08:05:31 +00:00
jlam
6354af1c5a Need at least 1.4.0.4nb1, which has the changed library names. 2002-08-27 18:20:27 +00:00
jlam
c413122961 Re-add aalib-x11/buildlink.mk with appropriate modifications to work with
the new aalib-x11 package.  SDL/buildlink.mk uses aalib-x11/buildlink.mk,
so we can't kill it, yet.
2002-08-27 18:18:33 +00:00
jlam
beaaa4d9a4 Share common pkgsrc bits between the aalib and aalib-x11 packages. Shrink
the aalib-x11 package to installing just the libraries and headers and to
install them with new names so that aalib-x11 and aalib no longer conflict.
Also, remove the aalib-x11/buildlink.mk file as it will be no longer used.
This solves part of pkg/16354.
2002-08-26 19:38:05 +00:00
jlam
efb93b17bd Merge changes in packages from the buildlink2 branch that have
buildlink2.mk files back into the main trunk.
2002-08-25 19:21:43 +00:00
cjep
0e5fd032fb On arm32 pull in gcc-2.95.3 to build. 2002-03-25 14:45:25 +00:00
agc
4da0b4eae0 Initial import of aalib-x11 1.4rc4, an ASCII art library with X11 support,
into the NetBSD Packages Collection.

AAlib is a portable ASCII Art library. From the AA project documentation:
"There are many problems of various kinds with video cards, low frequency
monitors, crashing graphical apps... AA-lib IS the solution. It works on a
terminal of any kind, it is fast and portable, it gives to you standard API.
It gives to your old hardware more power! "

Provided in PR 15266 by Lubomir Sedlacik <salo@Xtrmntr.org>
2002-01-30 11:31:42 +00:00