pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2009-09-12	Always set both --host and --build, a number of programs want to use	joerg	1	-1/+3
	a cross-compile like environment otherwise.
2008-11-29	One more variable for show-all-gnu-configure.	rillig	1	-1/+2

2008-02-07	Replaced _PKG_SILENT and _PKG_DEBUG with RUN.	rillig	1	-3/+3

2007-08-01	Begin adding some of the basic, non-intrusive pieces of the	joerg	1	-1/+4
	cross-compile support. - NATIVE_MACHINE_GNU_ARCH, NATIVE_LOWER_ARCH, NATIVE_MACHINE_ARCH, NATIVE_MACHINE_PLATFORM and NATIVE_MACHINE_GNU_PLATFORM work like the counterpars without NATIVE_ prefix. Expansion of NATIVE_LOWER_ARCH and NATIVE_MACHINE_ARCH is enforced early, so that MACHINE_ARCH can be overriden in mk.conf to specify the target architecture. - Provide a default of NO for USE_CROSS_COMPILE. This will be the main switch to activate cross-compiling and adding it now makes it possible to merge more of the patches for specific packages. - Set --build and --host when cross-compiling, the former using the just added variable NATIVE_MACHINE_GNU_PLATFORM. Supported-by: Google SoC 2007 Looks good: jlam@
2007-07-12	No longer pass install_sh in the environment to GNU configure scripts.	jlam	1	-2/+2
	We fix GNU configure script stupidity by directly replacing the stock install-sh script provided by the software with the BSD install-compatible sysutils/install-sh script. A new package-settable variable comes to life: INSTALL_SH_OVERRIDE is a list of files relative to WRKSRC which should be overridden by the install-sh script from sysutils/install-sh. If not defined or set to "no", then no files are overridden. Possible values: no, defined, undefined. Default value: defined when GNU_CONFIGURE is defined, undefined otherwise. Get rid of the install_sh tool, which is no longer needed.
2007-06-04	For GNU-style configure scripts, the environment variable install_sh	rillig	1	-2/+2
	must point to a shell script (as the name implies), not to a binary.
2007-03-15	For all those who are interested in the inner workings of pkgsrc, there	rillig	1	-1/+8
	is a new target "show-all" that fits to the existing "debug", "show-tools", "show-vars" targets. It prints a list of the variables that make up the public interface to pkgsrc. Running this target is especially useful if you want to do some things, you know that they must have been implemented but you don't know what it is called. It also shows the "class" of a variable (user-defined, package-defined, system-defined).
2007-03-15	Moved the definition of CONFIG_SHELL from gnu-configure.mk to configure.mk.	rillig	1	-2/+1
	Improved the documentation.
2006-07-05	Refactor configure, build, test and wrapper phases out of bsd.pkg.mk	jlam	1	-0/+100
	and into their own directories. Also do some cleanups with build/_build and pkginstall -- we get rid of _build and simply run pkginstall as part of the "build" target. Introduce a new mechanism to handle varying directory depths under ${WRKSRC} in which we find files to override, e.g. configure, config., libtool, etc. OVERRIDE_DIRDEPTH is a package-settable variable that specifies how far under ${WRKSRC} the various targets should look, and it defaults to "2". We preserve the meaning of the various _OVERRIDE variables, so if they are defined, then their values supersede the OVERRIDE_DIRDEPTH mechanism. devel/tla will need to specially set OVERRIDE_DIRDEPTH to 3 (see log for revision 1.1857 for bsd.pkg.mk -- to be done in a separate commit.