Metaconf uses the concept of "Unit" files (similar to an autoconf macro). When designing a package that uses metaconf, one just lists the "pieces" one needs, and the generator takes these things and (using "make -n", as I recall), finds all of the prerequisites, orders the tests, anad produces a Configure script. Unit files are nice because we could very easily include lots of them (including some obscure ones) as well as different ways to do the same thing in the metaconf distribution (Larry used one style of Endian testing and I used a different one; both styles are/were in the distribution). H
- Re: Requirements: configuration test dependencies Tom Tromey
- Re: Requirements: configuration test dependencies Alexandre Oliva
- Re: Requirements: configuration test dependencies Harlan Stenn
- Re: Requirements: configuration test dependencies Tom Tromey
- Re: Requirements: configuration test dependencies Akim Demaille
- Re: Requirements: configuration test dependen... Didier Verna
- Re: Requirements: configuration test depe... Akim Demaille
- Re: Requirements: configuration test... Didier Verna
- Re: Requirements: configuration ... Akim Demaille
- Re: Requirements: configurat... Didier Verna
- Re: Requirements: configurat... Akim Demaille
- Re: Requirements: configurat... Alexandre Oliva