On 3/8/07, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > Richard Lowe <richlowe at richlowe.net> wrote: > > > > In much the same way that we generate C sources via rpcgen, the > > > ksh93 build process could [diff/patch, rename, exclude, etc] the > > > files found in the baseline tree to create the OpenSolaris-specific > > > source tree. And then build that tree. > > > > No. > > No no no no no. > > No. > > > > This is not analogous to rpcgen, this is patching a fairly large component > > into the ON world *at build time*. Such that we don't actually have the > > sources we build in the tree at all, but instead have the original sources > > and a collection of hard to maintain, impossible to cscope, impossible to > > opengrok patches and scripts to perturb them into buildable form as part of > > the build. > > I am not sure what Roland did with ksh93, I did change my build system during > the last 6 months in a way that it now allows to "statically" install the > results of the autoconfiguration process in a way that allows all build > systems > to use my include files.
I think that is the same solution Roland is using. ksh93 is build once outside ON and the results of the autoconfiguration process is imported into ON separated into target-specific sub directories (i386, amd64, sparc, ...). Irek
