| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
correct make(1) program is invoked by pkgxmkmf.
|
|
used by pkgtools/xpkgwedge.
|
|
compiler (CC/CXX) if we're actually using imake to generate Makefiles
for building and installing software. This fixes errors in various
KDE-3.x packages that use imake for other purposes.
|
|
are checked for ${WRKDIR}, but all files are checked for ${TOOLS_DIR}
(assuming that ${TOOLS_DIR} is in ${WRKDIR}). Also, let CHECK_WRKREF_PKG
set the name of the package to check.
|
|
targets so that if they're overridden in the package Makefile, the
message is still printed.
|
|
to "do-distribution-patch" and "do-pkgsrc-patch", respectively, and
allow them to be overridden by the package Makefile. This allows for
more fine-grained overriding of the patch process.
|
|
(as may be the case if all options are platform specific). In that
case set PKG_OPTIONS to empty and skip the rest of the file.
Okayed by jlam.
|
|
are automatically undefined after the loop exits.
|
|
issue).
|
|
for a package and looks for references to the build directory. If
any such references are found and PKG_DEVELOPER is defined, then exit
with an error. This target is automatically run after a package is
installed if CHECK_WRKREF is "yes". The default value for CHECK_WRKREF
is "no".
You can specify certain files to be skipped during the check by setting
CHECK_WRKREF_SKIP to a list of shell globs. Installed files that
match these globs are skipped when running the check-wrkref target.
The original implementation was from Dan McMahill sent to me in private
email. I've added a few more bells and whistles for this commit. This
target will be helpful for catching any unwrapped files or mis-embedded
tool paths.
|
|
shell builtins, e.g. echo, false, test, true, since those tools don't
have a full path.
|
|
|
|
|
|
|
|
argument during argument merging.
|
|
* Improve the documentation.
* Avoid running commands during Makefile processing by using the :sh
modifier instead of defining variables using !=
* Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES
file to be modified.
* Use ${ID} and ${DATE}, which are provided by the tools framework and
avoid PATH issues.
|
|
portion of the path.
|
|
|
|
|
|
matches the template in bsd.builtin.mk. This causes USE_BUILTIN.pthread
to be cached, which is useful at least for debugging purposes.
|
|
|
|
into pkgsrc/doc/CHANGES.
The type of the entry depends on what CTYPE is set to, which defaults
to "Updated". Other possible values are "Added", "Renamed", "Moved",
and "Removed". An example usage would be:
cd /usr/pkgsrc/category/package
make changes-entry CTYPE=Added
after you added a new package, and similar for the others.
If NETBSD_LOGIN_NAME is not set in /etc/mk.conf, it defaults to
your local login name.
|
|
|
|
This also fixes the problem where the names of broken local patches
(in ${LOCALPATCHES}) weren't printed correctly in the error message.
|
|
|
|
|
|
|
|
Simplify it so that USE_BUILTIN.dl is simply IS_BUILTIN.dl except for
Darwin's special case. This makes PREFER_PKGSRC=yes work again on
NetBSD instead of causing USE_BUILTIN.dl=no to be set, which is
impossible.
|
|
-Wl,-rpath -Wl,/dir1:/dir2:/dir3
into:
-Wl,-rpath,/dir1 -Wl,-rpath,/dir2 -Wl,-rpath,/dir3
Do the same for -Wl,-R and -Wl,-rpath-link. This makes the wrapper
scripts pass the test in regress/buildlink-transform/rpath-merge.mk
and fixes PR pkg/27702.
|
|
|
|
|
|
|
|
"env" tool.
|
|
Also, some configure scripts use "ENV" to represent the path to the
"env" tool, which is probably bad since ENV has a special meaning to
/bin/sh. To workaround this, set ac_cv_path_ENV.
|
|
PKG_LEGACY_OPTIONS
PKG_OPTIONS_DEPRECATED_WARNINGS
|
|
|
|
|
|
|
|
are not part of the public interface.
|
|
|
|
While here, rename _cls_ to _grp_, as they are called groups.
|
|
|
|
mktemp with USE_TOOLS+=mktemp in the samba packages.
|
|
x11-clients.buildlink3.mk. Packages that need bdftopcf should say:
USE_TOOLS+= bdftopcf
|
|
through to dependencies, which caused dependencies to have improper
lists of tools required.
XXX This whole mess with MAKEFLAGS and which ones are passed along when
XXX running the install-depends target needs to be fixed for real.
|
|
the X11 distribution using imake into mk/buildlink3/imake-check.mk.
imake-check.mk calls out to a helper shell script mk/buildlink3/imake-check
that generates the required Imakefiles and runs imake. Remove the
now extraneous builtin-imake.mk files as the builtin.mk files can now
contain the name of the imake symbol to check.
|
|
|
|
|
|
|
