to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
or USE_X11BASE set, but don't include mk/x11.buildlink3.mk directly or
via buildlink3.mks
- introduce BUILDLINK_PREFIX.libXpm as alias for BUILDLINK_PREFIX.xpm
in the !modular case
- fix some cases where the check for libX11 couldn't work at all by using
C++ for compilation without including the proper headers
Verified using a full X11_TYPE=xorg bulk build without additional
breakage. Discussed with salo@, wiz@ and send to packages@ for feedback.
sablevm) as noted by Gary Duzan in PR pkg/30137
Fix PLIST issues, to properly deintall
Fix AWK snippets for print-PLIST
Bump PKGREVISION for sablevm and sablevm-classpath
that these directories will be conditionally removed (based on reference
counts), regardless of the value of PKG_CONFIG. Bump the PKGREVISION
for packages that were modified as a result.
file's sole purpose was to provide a dependency on pkg-config and set
some environment variables. Instead, turn pkg-config into a "tool"
in the tools framework, where the pkg-config wrapper automatically
adds PKG_CONFIG_LIBDIR to the environment before invoking the real
pkg-config.
For all package Makefiles that included pkg-config/buildlink3.mk, remove
that inclusion and replace it with USE_TOOLS+=pkg-config.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
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".
can easily coexist with other Java implementations. This basically means
that they are now installed under ${PREFIX}/java/sablevm and that a wrapper
is created under ${PREFIX}/bin (sablevm-java) to exec this VM.
list of changes since 1.1.1. AFAICT, it seems that the code has been sync'ed
with GNU classpath 0.08 and the installation has been modified to work "out
of the box" with sablevm (i.e., no need to create more symbolic links to let
the vm find the classes).
SableVM is a portable bytecode interpreter written in C, and implementing
the Java virtual machine specification, second edition. Its goals are to
be reasonably small, fast and efficient, as well as providing a well
designed and robust platform for conducting research.
This package contains the GTK binding required to run AWT and Swing
applications with sablevm-classpath and sablevm.
