> In the case of a build of APR, it's as simple as running three scripts > back to back: > > ./configure > make > make install > I know a make file is a script, but Gump doesn't consider launching the 'make' executable a script. I think I ought be able to add a <make entry that does launch it though, if needed.
> Then the fun starts. APR-util depends on APR, so the results of "make > install" above need to be made available to APR-util, and then both to > httpd, rinse, repeat. > > The RPM build is similar, you just replace the scripts above with: > > rpmbuild -tb apr-x.x.x.tar.gz. Hmm, ok, yet another thing to launch. We could put these all into simple (one liner) scripts, I guess. This is probaby better than Gump calling command lines 'cos there is a better chance to insert platform intelligence, if needed. > So in short: gump needs to be able to run one or more scripts. Ok, so if we encapsulated these command lines in scripts, then things are simple again (from a launching point of view). What about inputs/outputs though? Assume we can teach Gump about outputs of a build (libs, etc.) how does it 'feed' those into subsequent rinses? Environment variable? regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
