summaryrefslogtreecommitdiff
path: root/converters/libiconv/builtin.mk
AgeCommit message (Collapse)AuthorFilesLines
2008-02-27Greatly simplify the logic that tries to determine whether -lintljlam1-35/+34
needs -liconv in order to satisfy linkage requirements. This is now patterned after the approach taken with readline and termlib. Examples on NetBSD for a package that includes only gettext-lib/buildlink3.mk: PREFER_NATIVE= yes PREFER_PKGSRC= # empty # This uses the native gettext and native iconv, with: # BUILDLINK_LDADD.gettext == "-lintl" PREFER_NATIVE= yes PREFER_PKGSRC= iconv # This uses the native gettext and native iconv, with: # BUILDLINK_LDADD.gettext == "-lintl" PREFER_NATIVE= yes PREFER_PKGSRC= gettext # This uses the pkgsrc gettext and native iconv, with: # BUILDLINK_LDADD.gettext == "-lintl" PREFER_NATIVE= yes PREFER_PKGSRC= gettext iconv # This uses the pkgsrc gettext and pkgsrc iconv, with: # BUILDLINK_LDADD.gettext == "-lintl -liconv" PREFER_NATIVE= # empty PREFER_PKGSRC= yes # This uses the pkgsrc gettext and pkgsrc iconv, with: # BUILDLINK_LDADD.gettext == "-lintl -liconv" PREFER_NATIVE= iconv PREFER_PKGSRC= yes # This uses the pkgsrc gettext and native iconv, with: # BUILDLINK_LDADD.gettext == "-lintl" PREFER_NATIVE= gettext PREFER_PKGSRC= yes # This uses the native gettext and native iconv, with: # BUILDLINK_LDADD.gettext == "-lintl" PREFER_NATIVE= gettext iconv PREFER_PKGSRC= yes # This uses the native gettext and native iconv, with: # BUILDLINK_LDADD.gettext == "-lintl"
2008-02-27Whitespace.jlam1-6/+7
2007-11-07Fix version detection when the version number contains capital letters.minskim1-5/+5
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-2/+2
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-03-30Avoid extra stat() calls by not repeatedly checking whether a filejlam1-3/+3
exists on the disk -- we can just check whether a variable defined by find-files.mk is "__nonexistent__" or not.
2005-06-06Back out previous and reset the BUILTIN_VERSION.iconv variable instead.jlam1-3/+3
This should fix functioning on Linux systems that actually use GNU libiconv as the builtin iconv implementation.
2005-06-05Make BUILTIN_PKG.iconv follow what the comment says.minskim1-2/+2
2005-06-05Assume that DragonFly's native libiconv is good enough for pkgsrc, just asjmmv1-4/+5
we do for NetBSD. Patch from Joerg Sonnenberger.
2005-06-05In builtin.mk files, use _BLTN_ as the private namespace prefix.jlam1-11/+11
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam1-62/+85
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-24Rewrite to use find-libs.mk rename several variables to begin withjlam1-78/+75
_BLNK_ to properly namespace those variables, and rewrite BUILTIN_PKG.iconv computation to use one fewer awk invocation.
2005-05-22Simplify a condition.minskim1-3/+2
2005-05-22Use the iconv library in glibc on Linux even if USE_GNU_ICONV is set.minskim1-2/+3
2004-08-28Use the new BUILDLINK_TRANSFORM commands to more precisely state thejlam1-2/+2
intended transformation: use "rm" to remove an option, "rmdir" to remove all options containing a path starting with a given directory name, and "rename" to rename options to something else.
2004-06-04By default, assume that the native iconv on Linux systems usingreed1-1/+16
GLIBC supports GNU libiconv's API. So don't depend on pkgsrc's libiconv for it. This is normal: most other Linux distros don't provide a libiconv package. This was discussed on tech-pkg list over past two months. It has helped a few users under Linux where they had some problems with conflicts with their working iconv() support provided with libc and the libiconv package. This was okayed by maintainer, Rene Hexel. This still needs some improvement. Some packages still try to force libiconv usage even though not needed.
2004-04-26Do previous in a different way. We want USE_GNU_ICONV to always usejlam1-19/+73
a GNU libiconv, whether it be builtin or not, and PREFER_{NATIVE,PKGSRC} can be used to decide which iconv we use if USE_GNU_ICONV isn't defined. On NetBSD, the native iconv implementation (if it exists) is considered GNUish enough unless USE_GNU_ICONV is explicitly defined.
2004-04-26If USE_GNU_ICONV is defined, don't use builtin libiconv if ICONV_TYPE issnj1-15/+15
native.
2004-03-29Match the template builtin.mk file in bsd.builtin.mk, and make the twojlam1-9/+9
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links) use the new format correctly.
2004-03-10Split out the code that deals with checking whether the software isjlam1-0/+78
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.