Module dependencies

Module dependencies

[Jeffrey Walton]

Hi Everyone,

There are 1700+ modules according to --list. At 3 minutes (est.) a
test that would take 85 hours to complete.

I _think_ a speedup is, if module A uses B and C, then we can scratch
three off the list at a time. The problem I am having is, I'm having
trouble understand the output from --extract-dependencies and
--extract-recursive-dependencies.

What is the difference between these:

CASE 1:
./gnulib-tool --create-testdir --dir="${TEST_DIR}" iconv
Module list with included dependencies (indented):
    absolute-header
    accept
    accept-tests
    alloca
    alloca-opt
    alloca-opt-tests
    ...

CASE 2:
$ ./gnulib-tool --extract-dependencies iconv
havelib

CASE 3:
$ ./gnulib-tool --extract-recursive-dependencies iconv
havelib
iconv

In Case 1 there's a rich list of modules. Case 2 and Case 3 seem to be
missing dependencies. For example, --list shows:

$ ./gnulib-tool --list
...
alloca
alloca-opt
allocator
...

So Case 1 says alloca and alloca-opt are included and tested with
iconv. Case 2 and Case 3 say alloca and alloca-opt are not included
and therefore not tested with iconv.

What is the difference in outputs?

Jeff

Re: Module dependencies

[Bruno Haible]

Hi,

> So Case 1 says alloca and alloca-opt are included and tested with
> iconv. Case 2 and Case 3 say alloca and alloca-opt are not included
> and therefore not tested with iconv.

Try

  ./gnulib-tool --create-testdir --dir="${TEST_DIR}" iconv

vs.

  ./gnulib-tool --create-testdir --dir="${TEST_DIR}" --without-tests iconv

and look at the dependencies of 'iconv-tests' ...

Bruno