On Thu, 7 Apr 2005, Georg Schwarz wrote:

> could you maybe leak some more information about this wrapper/symlink
> directories work? It sounds a bit like this could solve many of the tools
> problems on IRIX 5.

I removed my comment above because I realized I was wrong about the
ordering (as mentioned in my followup email).

Anyways, this is really brief:

The PREPEND_PATH may include the WRAPPER_BINDIR (work/.wrapper/bin) for
tools like: as, cc, cpp, cxx, fc, imake and ld. (See
mk/wrapper/bsd.wrapper.mk.)

The PREPEND_PATH may include the BUILDLINK_BINDIR (work/.buildlink/bin)
for any executables to be buildlinked using BUILDLINK_FILES. For example,
see textproc/aspell/buildlink3.mk and textproc/libxml2/buildlink3.mk (for
BUILDLINK_FILES). (See mk/buildlink3/bsd.buildlink3.mk.)

The PREPEND_PATH may include the ${TOOLS_DIR}/bin (work/.tools/bin) for
executables like aclocal, autoconf, autoheader, autom4te, perl, patch,
makeinfo, make and more. Some are defined using the USE_GNU_TOOLS. (See
mk/tools.mk.)

The PREPEND_PATH may include the ${PKG_JAVA_HOME}/bin. (See mk/java-vm.mk.)

The PREPEND_PATH may include the bin/ directory for your compiler (like
${_GCC_DIR}/bin. (See mk/compiler/*.mk.)

Then mk/bsd.pkg.mk reverses the PREPEND_PATH to set PATH.

For example, the final PATH may look like:
work/.wrapper/bin work/.buildlink/bin work/.tools/bin work/.gcc/bin
${X11BASE}/bin ${LOCALBASE}/bin followed by your original PATH.

PATH is included in ALL_ENV and CONFIGURE_ENV and MAKE_ENV. So this new
PATH is used for the configure and build.

(It seems to me we have some duplicated functionality and this could be
simplified. Also for me the current mk/tools.mk is broken because it
assumes that some tools are installed and also defines some variables
wrong.)

 Jeremy C. Reed

 	  	 	 open source, Unix, *BSD, Linux training
	  	 	 http://www.pugetsoundtechnology.com/