CMake and finding external dependencies ( from Omniorb merge vs OS-X port)

On Monday 09 February 2009 16:21:36 Stephen Roderick wrote:
> I would advocate a long-term goal of no hard-coded paths anywhere in
> our CMake files. They should all come from external user customization
> of the build, either via environment variables or from optional user-
> specific CMake configuration files that add to CMake versions of said
> environtment variables (recently mentioned by a couple of people on
> the ML w.r.t. Windoze porting effort). There is a *lot* of CMake code
> in Orocos that uses hard-code paths ...

This is indeed the target our buildsystem must reach. Or by using externally
developed macros, or by fixing ours.