Commit graph

16 commits

Author SHA1 Message Date
David Howland
9921aed8ad USE_LANGUAGES+= c++ 2006-08-25 20:44:46 +00:00
Thomas Klausner
72f5c3ea90 Bump PKGREVISION and BUILDLINK_ABI_DEPENDS (where applicable)
for SDL shlib changes.
2006-06-12 16:28:54 +00:00
Yoshito Komatsu
3ac4fbc0ed Replace tech-pkg@NetBSD.org with pkgsrc-users@NetBSD.org. 2006-05-19 16:51:13 +00:00
Jeremy C. Reed
37f815a375 Change BUILDLINK_DEPENDS.foo to BUILDLINK_API_DEPENDS.foo.
Change BUILDLINK_RECOMMENDED.foo to BUILDLINK_ABI_DEPENDS.foo.

As discussed on tech-pkg.
2006-04-06 07:16:55 +00:00
Roland Illig
1ee539a984 Added RMD160 checksums. 2005-09-28 06:41:05 +00:00
Thomas Klausner
6ede639c74 Reset MAINTAINER -- he stopped working on pkgsrc. 2005-07-27 16:24:52 +00:00
Todd Vierling
5f60a41bb5 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:09:34 +00:00
Johnny C. Lam
84663f5da5 Mechanical conversion to use LIBTOOLIZE_PLIST (which defaults to "yes" in
pkgsrc).  LIBTOOL_LA_FILES is no more.
2004-09-23 05:59:29 +00:00
Todd Vierling
3258328d22 Convert manual libtool archive PLIST entries to dynamic entries using new
LIBTOOL_LA_FILES logic in bsd.pkg.mk.
2004-08-17 18:26:11 +00:00
Soren Jacobsen
ad3f962061 No longer used. 2004-04-12 02:35:12 +00:00
Min Sik Kim
be5ef4a932 Build fails on NetBSD-current. 2004-03-07 04:46:15 +00:00
Michal Pasternak
07730a5ad0 Add conflicts for upcoming kyra2 2004-03-07 02:45:14 +00:00
Michal Pasternak
55db94a245 bl3ify & import TODO 2004-03-07 02:38:00 +00:00
Soren Jacobsen
084e0938cf LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now shell globs relative to
WRKSRC.  LIBTOOL_OVERRIDE defaults to "libtool */libtool and */*/libtool,"
meaning that, in most packages, there's no need to set it.

So: Nuke tons of LIBTOOL_OVERRIDE=${WRKSRC} and adjust a few
SHLIBTOOL_OVERRIDEs (remove ${WRKSRC} from them).
2004-02-17 02:55:13 +00:00
Michal Pasternak
249efe7ff1 Correct buildlink2 .includes 2004-01-04 06:21:54 +00:00
Michal Pasternak
1d7663c154 Kyra - A Sprite Engine...
from a Slightly Different Point of View

What is a Sprite Engine? A Sprite Engine is the drawing and rendering
component of 2D and quasi-3D games. Examples of this kind of game are
Civilization, Donkey Kong (classic arcade), Pharaoh, Zeus, Warcraft, Diablo,
Frogger, and Pirates!, among many others. It is so called because the
"characters" or "little men" are referred to as "sprites".

Simple and Easy to Use. Kyra has a clean and simple C++ interface. Or at
least as simple as an engine can be. It comes with several examples to get
you started, as well as full documentation for the API and the tool chain.

Fully Featured. It is fully featured, supporting top-down, side, and
isometric rendering. It supports the 'Sprite' as its basic type, but also
supports Tiles and user-drawn Canvases. It can draw to a traditional bitmap
surface, and supports OpenGL hardware acceleration.

Industrial Strength. Kyra has a complete tool chain including a sprite
editor and encoder. It's fast and capable, with specialized code for
rendering and rectangle updates.
2004-01-04 06:20:34 +00:00