No subject

library directory (configuration-specific; for this example I'll use
debug): <output_dir>/third_party/zlib/1.2.3/lib/debug
bin files (again, configuration specific):
<output_dir>/third_party/zlib/1.2.3/bin/debug/zlib.dll

When I define a project (target) in CMake through my framework that
needs to use zlib as a dependency, instead of setting up includes,
libs, bins, etc all by hand, I simply pass it the alias and all of
that information is setup for me. So example:

define_project( my_project THIRD_PARTY zlib )

It's a ton of logic and all stuffed into CMake scripts as a framework,
so it's pretty inefficient. If we carried over that logic to CPackage
as I stated before, it can be made to be very efficient and
extensible. I can also carry over this logic across multiple platforms
easily and add native package handler support to CPackage in the case
of Linux.

You asked for ideas so I am giving you some. Hopefully it wasn't too
miserable to read :) Let me know what you think.