On Thu Aug 30 10:36:23 2007, particle wrote: > > below is a brief requirements list for these use cases. at this early > point in the design process, the first two use cases are so similar > we'll consider them together. > > 1&2 develop/maintain cross-compilation configuration: > ~ specify which configure steps are run > ~ specify order in which configure steps are run > ~ specify which options are passed to each configure step > ~ use human-readable data format and storage (e.g. flat files used in > my example code) > ~ provide central location for storage and organization of > cross-compilation configuration data (e.g. directory specified in my > example code) > > 3 run cross-compilation configuration: > ~ simple, documented method of invocation (e.g. C<perl Configure.pl > --config=dirname/filename>.) i'm not married to the option name >
I am working on this in the scriptconfigure branch. kid51
