On Wed, 7 Mar 2007 15:03:43 +0800 Peter Memishian wrote:
> (Note: I've removed the Makefiles, diffs, and obvious documentation files,
> as those are already being covered in other discussions.)
> > ./lib/*/common/features/*
> > ./lib/*/*/src/lib/*/FEATURE/*
features holds the compiled time iffe (configure) input files
FEATURES holds the compile time iffe output files
the FEATURES files are privately included by component specific
source (e.g., libast includes ./lib/*/*/src/lib/libast/FEATURE/*)
to build the component
in some cases a FEATURE/* file is installed as a .h file for use
by other components
unless the generated FEATURE files have been munged to work on all
solaris { platforms X compilers X compile-time-options } I don't
see how the architecture specific ones can be dropped
> > ./lib/libast/common/comp/conf.sh
> > ./lib/libast/common/comp/conf.tab
non-iffe generation script and input data
argument similar to features/FEATURE above
> > ./lib/libpp/common/gentab.sh
> > ./lib/libpp/common/pp.def
> > ./lib/libpp/common/pp.key
> > ./lib/libpp/common/pp.probe
> > ./lib/libpp/common/pp.tab
> > ./lib/libpp/common/ppsym.c
> > ./lib/libpp/common/probe.win32
if you want to use the ast msg* commands/libs to generate l18n message
catalogs from the source then these ast cpp support files will be
needed on at least one platform to generate the catalogs on that
platform
> > ./lib/libshell/common/include/env.h
> > ./lib/libshell/common/sh/env.c
> > ./lib/libshell/common/sh/bash.c
these files are are controlled by build-time options
if any of those options should change then the build will fail
e.g., suppose a downstream user wants to build ksh93 with bash compatibility
that user will have to grab the missing source from a non-solaris site
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
