summaryrefslogtreecommitdiff
path: root/x11/gtk
AgeCommit message (Collapse)AuthorFilesLines
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam2-4/+4
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.
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-04-27Fix AC_DEFUN argument quoting for automake 1.8 and newer. Addresseswiz2-1/+15
part of PR 30053. No PKGREVISION bump because most people won't care.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 checksums to the SHA1 ones.wiz1-1/+2
2004-10-04distinguish between gtk1 and gtk2 in COMMENT.grant1-2/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-4/+4
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-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-9/+1
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".
2004-05-29unused.kristerw1-29/+0
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-04-14Drop the disctinction of xdg and xdg-x11 from USE_DIRS POV. We can choosejmmv1-2/+2
which one is required in an automatic way by checking USE_X11BASE. This simplifies things and avoids possible problems in the future due to confusion.
2004-04-14Make use of the new USE_DIRS variable, instead of directly depending on thejmmv1-3/+2
*-dirs packages.
2004-03-29Add a BUILDLINK_PKGBASE.<pkg> definition where it's not equal to <pkg>,jlam1-1/+2
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example buildlink[23].mk files in bsd.buildlink[23].mk.
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-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-11Remove info files entries from PLIST.seb1-9/+1
2004-03-08Handle some shared directories by depending on (or updating dependancies tojmmv2-4/+6
the latest versions) xdg-dirs, xdg-x11-dirs or gnome*-dirs. Bump PKGREVISION.
2004-03-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-5/+8
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-14PKGCONFIG_OVERRIDE is relative to WRKSRC.jmmv1-3/+3
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-02-14remove unneeded CONFIG_{GUESS,SUB}_OVERRIDE, as bsd.pkg.mk does thisgrant1-2/+1
automatically now.
2004-01-24replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.grant1-2/+2
2004-01-24Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. Injlam1-2/+2
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched.
2004-01-18Move some @exec/@unexec logic out of the PLIST into an INSTALL file.jlam3-10/+28
2004-01-15Don't force an update on people who have working versions of gtk installed.rh2-4/+6
Revert the previous and use BUILDLINK_RECOMMENDED instead of DEPENDS.
2004-01-15During the integration of buildlink3 the package was broken for some time.mrauch3-6/+6
Bump the PKGREVISION to force installation of a known working version.
2004-01-07bl3ify againjlam1-5/+6
2004-01-07Revert bl3ification until unbuildlink problems noted on tech-pkg@jlam1-7/+6
"Re: graphics/gdk-pixbuf can't find <gdk/gdk.h> build problem" are fixed.
2004-01-05bl3ifyjlam1-6/+7
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-10/+7
2004-01-03Initial sprinkling of work-in-progress buildlink3.mk files for using thejlam1-0/+24
buildlink3 framework.
2003-12-29improve descriptions of glib/gtk packages. taken straight fromgrant1-2/+9
www.gtk.org.
2003-12-08Didn't realize that some *-config scripts likereed1-3/+2
imlib-config were dynamic by running another *-config script. This fix is to remove the buildlinking of gtk-config, so imlib-config would work. As mention by Juan RP on tech-pkg, imlib's build could use CONFIGURE_ENV+= GTK_CONFIG="${PREFIX}/bin/gtk-config" to make sure that correct gtk-config is used. Because gtk-config was broken, imlib couldn't build. Probably x11/gtk's PKG_REVISION should by bumped? I need to look to see if smpeg-config is broken too (due to sdl-config path).
2003-12-03Make sure the *-config scripts are buildlinked too.reed1-2/+3
(As discussed on tech-pkg in late October; okay'd by wiz then.)
2003-10-04Fixes for Darwin: add CONFIG_SUB_OVERRIDE, don't use X shared memorydanw4-5/+20
extension, and tweak the gtk-config patch so it's still syntactically correct after RPATH_FLAG stripping
2003-08-09USE_NEW_TEXINFO is unnecessary now.seb1-2/+1
2003-08-08COMMENT tweak.grant1-2/+2
2003-07-30when using LIBTOOL_OVERRIDE in preference to LTCONFIG_OVERRIDE, let'sgrant1-2/+2
at least set it to ${WRKSRC}/libtool :) fixes install on Linux.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-07-13PKGREVISION bump for libiconv update.wiz2-4/+4
2003-06-25Convert to USE_NEW_TEXINFO; switch to LIBTOOL_OVERRIDE while here.wiz2-8/+4
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2003-05-19whitespace. no functional change.kei1-2/+2
2003-05-05Line up PKGREVISION whitespace.jmmv1-2/+2
2003-05-02Dependency bumps, needed because of devel/pth's major bump, and relatedwiz2-4/+4
dependency bumps.
2003-04-27Lint: USE_PKGLOCALEDIR=yescjep1-1/+2
2003-03-14(1) Publicly export the value of _OPSYS_RPATH_NAME as RPATH_FLAG;jlam1-2/+2
Makefiles simply need to use this value often, for better or for worse. (2) Create a new variable FIX_RPATH that lists variables that should be cleansed of -R or -rpath values if ${_USE_RPATH} is "no". By default, FIX_RPATH contains LIBS, X11_LDFLAGS, and LDFLAGS, and additional variables may be appended from package Makefiles.
2002-12-19update MASTER_SITES.grant1-3/+2
2002-11-14dylan-* has been converted to buildlink2, so no more packages use thisjlam1-58/+0
file any longer.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-10 15:52:06 +0000