| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
|
|
|
|
|
|
|
|
Price:
The Shapefile C Library provides the ability to write simple C programs
for reading, writing and updating (to a limited extent) ESRI
Shapefiles, and the associated attribute file (.dbf). The Shapefile
format is a working and interchange format promulgated by ESRI for
simple vector data with attributes.
|
|
|
|
Some BUILDLINK_RECOMMENDED bumps done also.
(If I missed any, please let me know -- and let me know a good
way to automate this.)
|
|
with -Werror.
|
|
|
|
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".
|
|
should fix install error detected in bulk build
|
|
|
|
|
|
Should fix bulk build.
|
|
|
|
|
|
|
|
|
|
garmin-utils is a set of utilities for transferring waypoints, routes,
and tracks to and from Garmin GPS receivers.
|
|
|
|
Closes PR 26422 by Iain Hibbert.
|
|
|
|
|
|
|
|
Use CXX (instead of CC) as linker.
|
|
|
|
|
|
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
|
|
Tiff is backward compatible, but was broken on amd64 platform
so this makes sure new tiff is used.
|
|
|
|
brook at biology dot nmsu dot edu and his team at NMSU.
MapServer is an OpenSource development environment for building spatially
enabled Internet applications. It now supports MapScript which allows popular
scripting languages such as Perl, Python, Tk/Tcl, Guile and even Java to
access the MapServer C API. MapScript provides a rich environment for
developing applications that integrate disparate data.
|
|
|
|
|
|
brook at biology dot nmsu dot edu and his team at NMSU.
Vis5D is a system for interactive visualization of large 5-D gridded data sets
such as those produced by numerical weather models. One can make isosurfaces,
contour line slices, colored slices, volume renderings, etc of data in a 3-D
grid, then rotate and animate the images in real time. There is also a feature
for wind trajectory tracing, a way to make text anotations for publications,
support for interactive data analysis, etc. GRASS can import and export Vis5D
raster data.
|
|
|
|
|
|
brook at biology dot nmsu dot edu and his team at NMSU.
The gpsutils package covers some small applications to capture and convert
data from a Garmin GPS receiver. These are based on a included more general
GPS library (in C).
|
|
|
|
Initial import of gpspoint, one of the many packages provided by
brook at biology dot nmsu dot edu and his team at NMSU.
This package provides a program and library to download and upload waypoints,
routes, and tracks to and from your GPS device. Upload and download is
possible via the GARMIN interface. Current position obtainable via the NMEA
Interface, supported by most GPS devices.
|
|
|
