kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/pkgtools/xpkgwedge/Makefile

70 lines
2 KiB
Makefile
Raw Normal View History

Refer doc/pkgsrc.html instead of Packages.txt (HOMEPAGE variable).
2005-05-08 00:24:04 +02:00
# $NetBSD: Makefile,v 1.55 2005/05/07 22:24:04 wiz Exp $
Add xpkgwedge, an experimental patch that enables the build of X11 pkgs (even imake ones) that will install in /usr/pkg instead of /usr/X11R6. This is NOT (yet?) the standard X11 pkg build procedure, but it does provide a "way out" for users that do not want to pollute their /usr/X11R6 tree with pkgs.
1998-06-26 18:39:23 +02:00
I don't know why, but using XFree86 or xorg from pkgsrc, doesn't get the correct link flags, anyway adding ExtraLoadFlags seems to fix this. Bump version to 1.12 (XFree86/xorg fix).
2004-07-31 03:42:06 +02:00
DISTNAME= xpkgwedge-1.12
Add "pkgtools" to "${CATEGORIES}".
1998-09-27 20:37:51 +02:00
CATEGORIES= pkgtools devel x11
Update xpkgwedge to 1.0 and make appropriate changes to bsd.pkg.mk to handle the new version of xpkgwedge. Changes from xpkgwedge 0.4: * Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to pick up X11 config files in $(PREFIX)/lib/X11/config before the ones in the standard X11 tree. * Install a program called "pkgxmkmf" that's actually xmkmf, but checks in $(PREFIX)/lib/X11/config before the standard X11 config directory. * Create the host.def file in $(PREFIX)/lib/X11/config instead of always in ${X11BASE}/lib/X11/config. The benefits of this are: 1) xpkgwedge can now install into $(PREFIX) instead of always into $(X11BASE). 2) Keeps the X11 tree "pure", and doesn't affect people who want to run xmkmf and not include all the xpkgwedge stuff, even if it's installed. 3) Packages that install config files (lesstif, xview-config) can now do so in $(PREFIX). 4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and (hopefully) no other changes, if they want to use the config files in xpkgwedge'd packages.
2000-10-23 19:32:06 +02:00
MASTER_SITES= # empty
DISTFILES= # empty
Add xpkgwedge, an experimental patch that enables the build of X11 pkgs (even imake ones) that will install in /usr/pkg instead of /usr/X11R6. This is NOT (yet?) the standard X11 pkg build procedure, but it does provide a "way out" for users that do not want to pollute their /usr/X11R6 tree with pkgs.
1998-06-26 18:39:23 +02:00
s/netbsd.org/NetBSD.org/
2003-07-18 00:50:55 +02:00
MAINTAINER= jlam@NetBSD.org
Refer doc/pkgsrc.html instead of Packages.txt (HOMEPAGE variable).
2005-05-08 00:24:04 +02:00
HOMEPAGE= ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/doc/pkgsrc.html
s,/usr/X11R6/,$${X11BASE}, in COMMENT. yes, this deliberately does not expand ${X11BASE}, as that would lead to the same confusion (X11R6 vs. openwin, etc.) when we use this pkg's COMMENT on the web site/search.
2003-10-18 12:12:09 +02:00
COMMENT= Allows X11 pkgs to be built and used outside of $${X11BASE}
Add xpkgwedge, an experimental patch that enables the build of X11 pkgs (even imake ones) that will install in /usr/pkg instead of /usr/X11R6. This is NOT (yet?) the standard X11 pkg build procedure, but it does provide a "way out" for users that do not want to pollute their /usr/X11R6 tree with pkgs.
1998-06-26 18:39:23 +02:00
Update pkgtools/xpkgwedge to 1.9. Changes from version 1.8 are making this package work in a pkgviews world by looking for imake config files in ${PREFIX}/lib/X11/config, then ${VIEWBASE}/lib/X11/config, then ${X11BASE}/lib/X11/config. The second directory is where some packages may share a commonly-editted host.def file.
2004-01-04 00:34:19 +01:00
PKG_INSTALLATION_TYPES= overwrite pkgviews
Move WRKSRC definition away from the first paragraph in a Makefile.
2004-01-20 13:18:15 +01:00
WRKSRC= ${WRKDIR}
Update xpkgwedge to 1.0 and make appropriate changes to bsd.pkg.mk to handle the new version of xpkgwedge. Changes from xpkgwedge 0.4: * Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to pick up X11 config files in $(PREFIX)/lib/X11/config before the ones in the standard X11 tree. * Install a program called "pkgxmkmf" that's actually xmkmf, but checks in $(PREFIX)/lib/X11/config before the standard X11 config directory. * Create the host.def file in $(PREFIX)/lib/X11/config instead of always in ${X11BASE}/lib/X11/config. The benefits of this are: 1) xpkgwedge can now install into $(PREFIX) instead of always into $(X11BASE). 2) Keeps the X11 tree "pure", and doesn't affect people who want to run xmkmf and not include all the xpkgwedge stuff, even if it's installed. 3) Packages that install config files (lesstif, xview-config) can now do so in $(PREFIX). 4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and (hopefully) no other changes, if they want to use the config files in xpkgwedge'd packages.
2000-10-23 19:32:06 +02:00
EXTRACT_ONLY= # empty
These packages don't use any compilers, so set USE_LANGUAGES to an empty value.
2004-02-02 11:08:43 +01:00
USE_LANGUAGES= # empty
Update xpkgwedge to 1.0 and make appropriate changes to bsd.pkg.mk to handle the new version of xpkgwedge. Changes from xpkgwedge 0.4: * Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to pick up X11 config files in $(PREFIX)/lib/X11/config before the ones in the standard X11 tree. * Install a program called "pkgxmkmf" that's actually xmkmf, but checks in $(PREFIX)/lib/X11/config before the standard X11 config directory. * Create the host.def file in $(PREFIX)/lib/X11/config instead of always in ${X11BASE}/lib/X11/config. The benefits of this are: 1) xpkgwedge can now install into $(PREFIX) instead of always into $(X11BASE). 2) Keeps the X11 tree "pure", and doesn't affect people who want to run xmkmf and not include all the xpkgwedge stuff, even if it's installed. 3) Packages that install config files (lesstif, xview-config) can now do so in $(PREFIX). 4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and (hopefully) no other changes, if they want to use the config files in xpkgwedge'd packages.
2000-10-23 19:32:06 +02:00
NO_CONFIGURE= # defined
NO_CHECKSUM= # defined
Add xpkgwedge, an experimental patch that enables the build of X11 pkgs (even imake ones) that will install in /usr/pkg instead of /usr/X11R6. This is NOT (yet?) the standard X11 pkg build procedure, but it does provide a "way out" for users that do not want to pollute their /usr/X11R6 tree with pkgs.
1998-06-26 18:39:23 +02:00
Make sure LOCALBASE and X11BASE are defined before comparing them. (Thank you, Takahiro.)
2004-01-04 05:51:47 +01:00
.include "../../mk/bsd.prefs.mk"
xpkgwedge is not needed when X11BASE is LOCALBASE, so use PKG_SKIP_REASON. (Okay'd by jlam@). (Next I need to make sure that MesaLib and Xrender are not installed when using wip/XFree86-libs.)
2004-01-04 00:51:08 +01:00
.if ${LOCALBASE} == ${X11BASE}
PKG_SKIP_REASON+= "xpkgwedge is not needed when X11BASE is LOCALBASE"
.endif
Let xpkgwedge to create a symlink ${PREFIX}/bin/mkfontscale, which is required to install fonts/jmk-fonts and fonts/sgi-fonts with recent X. Suggested by Kibum Han. Also add mkfontscale to CONFLICTS because mkfontscale installs bin/mkfontscale. Bump PKGVERSION to 1.11.
2004-06-15 04:27:10 +02:00
.if exists(${X11BASE}/bin/mkfontscale)
CONFLICTS+= mkfontscale-[0-9]*
.endif
Add definitions for DEINSTALL_EXTRA_TMPL and INSTALL_EXTRA_TMPL if USE_PKGINSTALL is "YES". bsd.pkg.install.mk will no longer automatically pick up a INSTALL/DEINSTALL script in the package directory and assume that you want it for the corresponding *_EXTRA_TMPL variable.
2003-08-31 00:51:11 +02:00
USE_X11= YES
USE_PKGINSTALL= YES
DEINSTALL_EXTRA_TMPL+= ${.CURDIR}/DEINSTALL
INSTALL_EXTRA_TMPL+= ${.CURDIR}/INSTALL
Update the host.def file during view (de)installation. Also deal with the font program symlinks at both view-deinstall and normal deinstallation time since the files aren't listed in the PLIST (the font programs are handled completely by the INSTALL/DEINSTALL scripts).
2003-11-23 07:46:54 +01:00
INSTALLATION_DIRS= bin lib/X11/config
Make the REQ and MESSAGE files specifiable from package Makefiles, as REQ_FILE and MESSAGE_FILE respectively. Modify xpkgwedge to create its MESSAGE_FILE in the WRKDIR.
1998-09-17 17:47:08 +02:00
Symlink/remove bdftopcf, fstobdf, and mkfontdir in the INSTALL/DEINSTALL scripts so that they are properly added and removed if xpkgwedge is installed as a binary package. Also, add some protection against the case where ${X11BASE} == ${PREFIX} by checking this isn't true before removing these font-manipulation programs.
2002-02-26 22:49:05 +01:00
# FONT_PROGS are symlinked from ${X11BASE}/bin to ${PREFIX}/bin to allow
# ${PREFIX}/bin/${prog} to always work.
#
Let xpkgwedge to create a symlink ${PREFIX}/bin/mkfontscale, which is required to install fonts/jmk-fonts and fonts/sgi-fonts with recent X. Suggested by Kibum Han. Also add mkfontscale to CONFLICTS because mkfontscale installs bin/mkfontscale. Bump PKGVERSION to 1.11.
2004-06-15 04:27:10 +02:00
FONT_PROGS= bdftopcf fstobdf mkfontdir mkfontscale
Symlink/remove bdftopcf, fstobdf, and mkfontdir in the INSTALL/DEINSTALL scripts so that they are properly added and removed if xpkgwedge is installed as a binary package. Also, add some protection against the case where ${X11BASE} == ${PREFIX} by checking this isn't true before removing these font-manipulation programs.
2002-02-26 22:49:05 +01:00
Update pkgtools/xpkgwedge to 1.9. Changes from version 1.8 are making this package work in a pkgviews world by looking for imake config files in ${PREFIX}/lib/X11/config, then ${VIEWBASE}/lib/X11/config, then ${X11BASE}/lib/X11/config. The second directory is where some packages may share a commonly-editted host.def file.
2004-01-04 00:34:19 +01:00
FILES_SUBST+= VIEWBASE=${VIEWBASE}
Modernize this package a bit: * Use bsd.pkg.install.mk instead of supplying custom INSTALL/DEINSTALL scripts. * Note that this package doesn't really use buildlink. * Remove ancient BUILDLINK_DEPENDS= line at the bottom of the file that we no longer need since the buildlink1 days of yore.
2003-08-30 13:08:22 +02:00
FILES_SUBST+= FONT_PROGS=${FONT_PROGS:Q}
FILES_SUBST+= MAKE=${MAKE_PROGRAM:Q}
Add xpkgwedge, an experimental patch that enables the build of X11 pkgs (even imake ones) that will install in /usr/pkg instead of /usr/X11R6. This is NOT (yet?) the standard X11 pkg build procedure, but it does provide a "way out" for users that do not want to pollute their /usr/X11R6 tree with pkgs.
1998-06-26 18:39:23 +02:00
I don't know why, but using XFree86 or xorg from pkgsrc, doesn't get the correct link flags, anyway adding ExtraLoadFlags seems to fix this. Bump version to 1.12 (XFree86/xorg fix).
2004-07-31 03:42:06 +02:00
post-extract:
@${CP} ${FILESDIR}/xpkgwedge.def ${WRKSRC}
Update xpkgwedge to 1.0 and make appropriate changes to bsd.pkg.mk to handle the new version of xpkgwedge. Changes from xpkgwedge 0.4: * Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to pick up X11 config files in $(PREFIX)/lib/X11/config before the ones in the standard X11 tree. * Install a program called "pkgxmkmf" that's actually xmkmf, but checks in $(PREFIX)/lib/X11/config before the standard X11 config directory. * Create the host.def file in $(PREFIX)/lib/X11/config instead of always in ${X11BASE}/lib/X11/config. The benefits of this are: 1) xpkgwedge can now install into $(PREFIX) instead of always into $(X11BASE). 2) Keeps the X11 tree "pure", and doesn't affect people who want to run xmkmf and not include all the xpkgwedge stuff, even if it's installed. 3) Packages that install config files (lesstif, xview-config) can now do so in $(PREFIX). 4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and (hopefully) no other changes, if they want to use the config files in xpkgwedge'd packages.
2000-10-23 19:32:06 +02:00
do-build:
Modernize this package a bit: * Use bsd.pkg.install.mk instead of supplying custom INSTALL/DEINSTALL scripts. * Note that this package doesn't really use buildlink. * Remove ancient BUILDLINK_DEPENDS= line at the bottom of the file that we no longer need since the buildlink1 days of yore.
2003-08-30 13:08:22 +02:00
@${SED} ${FILES_SUBST_SED} ${FILESDIR}/pkgxmkmf.in > ${WRKDIR}/pkgxmkmf
Add xpkgwedge, an experimental patch that enables the build of X11 pkgs (even imake ones) that will install in /usr/pkg instead of /usr/X11R6. This is NOT (yet?) the standard X11 pkg build procedure, but it does provide a "way out" for users that do not want to pollute their /usr/X11R6 tree with pkgs.
1998-06-26 18:39:23 +02:00
I don't know why, but using XFree86 or xorg from pkgsrc, doesn't get the correct link flags, anyway adding ExtraLoadFlags seems to fix this. Bump version to 1.12 (XFree86/xorg fix).
2004-07-31 03:42:06 +02:00
.if defined(X11_TYPE) && !empty(X11_TYPE:Mxorg) || \
defined(X11_TYPE) && !empty(X11_TYPE:MXFree86)
Replace RPATH_FLAG with LINKER_RPATH_FLAG and COMPILER_RPATH_FLAG, which are the full option names used to set rpath directives for the linker and the compiler, respectively. In places were we are invoking the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is inserted in case the flag is a word, e.g. -rpath. The default values of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the compiler that you use. They may be overridden on a ${OPSYS}-specific basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG, respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
2004-08-27 08:29:06 +02:00
X11TYPEFLAGS?= -L${X11BASE}/lib ${COMPILER_RPATH_FLAG}${X11BASE}/lib
I don't know why, but using XFree86 or xorg from pkgsrc, doesn't get the correct link flags, anyway adding ExtraLoadFlags seems to fix this. Bump version to 1.12 (XFree86/xorg fix).
2004-07-31 03:42:06 +02:00
SUBST_CLASSES= fix
SUBST_STAGE.fix= post-patch
SUBST_FILES.fix= xpkgwedge.def
SUBST_SED.fix= -e "s|@X11TYPEFLAGS@|${X11TYPEFLAGS}|"
.else # X11_TYPE == XFree86 || X11_TYPE == xorg.
SUBST_CLASSES= foo
SUBST_STAGE.foo= post-patch
SUBST_FILES.foo= xpkgwedge.def
SUBST_SED.foo= -e "s|\#define ExtraLoadFlags @X11TYPEFLAGS@||"
.endif # X11_TYPE == native.
Update xpkgwedge to 1.0 and make appropriate changes to bsd.pkg.mk to handle the new version of xpkgwedge. Changes from xpkgwedge 0.4: * Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to pick up X11 config files in $(PREFIX)/lib/X11/config before the ones in the standard X11 tree. * Install a program called "pkgxmkmf" that's actually xmkmf, but checks in $(PREFIX)/lib/X11/config before the standard X11 config directory. * Create the host.def file in $(PREFIX)/lib/X11/config instead of always in ${X11BASE}/lib/X11/config. The benefits of this are: 1) xpkgwedge can now install into $(PREFIX) instead of always into $(X11BASE). 2) Keeps the X11 tree "pure", and doesn't affect people who want to run xmkmf and not include all the xpkgwedge stuff, even if it's installed. 3) Packages that install config files (lesstif, xview-config) can now do so in $(PREFIX). 4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and (hopefully) no other changes, if they want to use the config files in xpkgwedge'd packages.
2000-10-23 19:32:06 +02:00
do-install:
${INSTALL_DATA_DIR} ${PREFIX}/lib/X11/config
I don't know why, but using XFree86 or xorg from pkgsrc, doesn't get the correct link flags, anyway adding ExtraLoadFlags seems to fix this. Bump version to 1.12 (XFree86/xorg fix).
2004-07-31 03:42:06 +02:00
${INSTALL_DATA} ${WRKSRC}/xpkgwedge.def ${PREFIX}/lib/X11/config
Update xpkgwedge to 1.0 and make appropriate changes to bsd.pkg.mk to handle the new version of xpkgwedge. Changes from xpkgwedge 0.4: * Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to pick up X11 config files in $(PREFIX)/lib/X11/config before the ones in the standard X11 tree. * Install a program called "pkgxmkmf" that's actually xmkmf, but checks in $(PREFIX)/lib/X11/config before the standard X11 config directory. * Create the host.def file in $(PREFIX)/lib/X11/config instead of always in ${X11BASE}/lib/X11/config. The benefits of this are: 1) xpkgwedge can now install into $(PREFIX) instead of always into $(X11BASE). 2) Keeps the X11 tree "pure", and doesn't affect people who want to run xmkmf and not include all the xpkgwedge stuff, even if it's installed. 3) Packages that install config files (lesstif, xview-config) can now do so in $(PREFIX). 4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and (hopefully) no other changes, if they want to use the config files in xpkgwedge'd packages.
2000-10-23 19:32:06 +02:00
${INSTALL_SCRIPT} ${WRKSRC}/pkgxmkmf ${PREFIX}/bin/pkgxmkmf
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink