[CMake] The tao of find_package

[Dan Kegel]

Hi folks,
I'm just starting to play with cmake.  (I've used autotools, make,
scons, and gyp before.)  I've been looking at the docs off and on for
a couple days, playing
with toy examples and building a few things already converted to cmake.

The project I'm building consists of about ten separate libraries.
They used to have one (shaky) Makefile / xcode / visual studio project
per platform, but we're looking at using cmake to try unifying things.

At first we just wrote one CMakeLists.txt for each library, wrote a
FindXXX.cmake for each, use find_package() everywhere, and drove
the whole build with a shell script that invoked cmake and make once
for each library.
That's fine, but since the shell script doesn't do dependencies, it's not
very efficient.

Now we're trying to replace the shell script with a ueber-CMakeList.txt that
just does add_subdirectory() on the ten libraries.  The question is:
find_package() appears to be designed for finding *things that are already built
and installed*, not other libraries you might have to build in the
same make session.

Am I right in assuming that things I might want to build with my one big 'make'
shouldn't be located with find_package()?

Thanks,
Dan