28.5. Where is SCons Searching for Libraries? the `--debug=findlibs` Option
Prev | Chapter 28. Troubleshooting | Next

## 28.5. Where is SCons Searching for Libraries? the `--debug=findlibs` Option

To get some insight into what library names SCons is searching for, and in which directories it is searching, Use the `--debug=findlibs` option. Given the following input `SConstruct` file:

    env = Environment(LIBPATH = ['libs1', 'libs2'])
    env.Program('prog.c', LIBS=['foo', 'bar'])

And the libraries `libfoo.a` and `libbar.a` in `libs1` and `libs2`, respectively, use of the `--debug=findlibs` option yields:

    % scons -Q --debug=findlibs
      findlibs: looking for 'libfoo.a' in 'libs1' ...
      findlibs: ... FOUND 'libfoo.a' in 'libs1'
      findlibs: looking for 'libfoo.so' in 'libs1' ...
      findlibs: looking for 'libfoo.so' in 'libs2' ...
      findlibs: looking for 'libbar.a' in 'libs1' ...
      findlibs: looking for 'libbar.a' in 'libs2' ...
      findlibs: ... FOUND 'libbar.a' in 'libs2'
      findlibs: looking for 'libbar.so' in 'libs1' ...
      findlibs: looking for 'libbar.so' in 'libs2' ...
    cc -o prog.o -c prog.c
    cc -o prog prog.o -Llibs1 -Llibs2 -lfoo -lbar

Prev | Up | Next
28.4. How is SCons Constructing the Command Lines It Executes? the `--debug=presub` Option | Home | 28.6. Where is SCons Blowing Up? the `--debug=stacktrace` Option