summaryrefslogtreecommitdiff
path: root/graphics/glu/buildlink3.mk
AgeCommit message (Collapse)AuthorFilesLines
2004-10-07Extra PKGREVISION bump to cover the libtool/compiler-wrapper problems.tv1-2/+2
Since dependencies were actually failing to build, they fortunately don't require PKGREVISION bumps themselves.
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-1/+2
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.
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-3/+2
by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-15Move the definitions of MESA_REQD and _MESA_REQD to Mesa/version.mk andjlam1-2/+2
modify {MesaLib,glu}/{buildlink3,builtin}.mk accordingly. Also add the dependency on {MesaLib,glu}>=${_MESA_REQD} to the builtin.mk files so that we correctly check the built-in Mesa version against the dependency requirements.
2004-03-10Split out the code that deals with checking whether the software isjlam1-90/+8
built-in or not into a separate builtin.mk file. The code to deal checking for built-in software is much simpler to deal with in pkgsrc. The buildlink3.mk file for a package will be of the usual format regardless of the package, which makes it simpler for packagers to update a package. The builtin.mk file for a package must define a single yes/no variable USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether to use the built-in software or to use the pkgsrc software.
2004-02-18Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in thejlam1-16/+18
environment overrides all other settings.
2004-02-12Create a new variable PREFER_NATIVE that has the opposite semanticsjlam1-3/+13
as PREFER_PKGSRC. Preferences are determined by the most specific instance of the package in either PREFER_PKGSRC or PREFER_NATIVE. If a package is specified in neither or in both variables, then PREFER_PKGSRC has precedence over PREFER_NATIVE.
2004-02-12Reorganize code so that any dependencies are checked as part of decidingjlam1-28/+30
whether the software is built-in or not. This facilitates implementing the forthcoming PKGSRC_NATIVE variable.
2004-02-11Turn MESA_REQD back into a public variable, and make it take a list ofjlam1-2/+2
values that MesaLib/buildlink3.mk converts into a single _MESA_REQD that is the highest version required. If including the Mesa/buildlink3.mk file, then require the same version of Mesa as required by glut.
2004-02-10Require at least the version of Mesa that's installed by the base systemjlam1-1/+2
if it's used.
2004-02-10Privatise MESA_REQD.jlam1-3/+3
2004-02-10The pkgsrc version of Mesa that last bumped shlib majors was 6.0.jlam1-2/+2
2004-02-06If we're passing through MAKEFLAGS variables whose values may containjlam1-3/+3
spaces, use the :Q modifier instead of double-quoting the value. This avoids breakage when executing the just-in-time su targets.
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam1-5/+3
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam1-5/+4
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam1-1/+9
BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
2004-01-24Support BUILDLINK_DEPENDS.<pkg> being a list of values.jlam1-5/+9
2004-01-24If we use the XFree86-supplied GL and GLU libraries, then we are using X11.jlam1-1/+2
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-05Sow BUILDLINK_USE_BUILTIN.<pkg> and reap _NEED_<PKG> variables.jlam1-18/+17
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-5/+5
2003-09-30Match the buildlink3.mk guidelines set out in revision 1.22 ofjlam1-6/+5
bsd.buildlink3.mk.
2003-09-30Conform to latest buildlink3.mk guidelines using *_BUILDLINK3_MK guardsjlam1-10/+18
to protect more parts of buildlink3.mk files against multiple inclusion.
2003-09-28Rewrite buildlink3.mk files to match the updated buildlink3.mk templatejlam1-8/+9
in bsd.buildlink3.mk: the *_BUILDLINK3_MK multiple inclusion guards are removed and we ensure that things that should be defined only once really are defined only once by using section-specific or variable-specific guards.
2003-09-14Provide definitions for BUILDLINK_PREFIX.<pkg> when the dependency may bejlam1-1/+3
satisfied by a base system (X11R6) component.
2003-09-13Need to use :C instead of :S to get the "pop" action to work properly.jlam1-2/+2
2003-09-07buildlink3.mk file needed by x11-links.jlam1-0/+69
generated by cgit v1.2.3 (git 2.39.1) at 2025-03-11 04:21:38 +0000