[CMake] Creating a static lib from other static libs, HOW?

[Brandon Van Every]

On 9/23/07, Juan Sanchez <Juan.Sanchez at amd.com> wrote:
>
> What is the appropriate email list for doing things in cmake for a
> particular architecture, like Unix?

Of course this one is.  Plenty of system-specific stuff is discussed here.

> There is a rich history in many disciplines where people need to address
> a compelling need in a specific case.  Once the immediate need is
> addressed, the system can be extended for the general case.
>
> In some instances, it is impossible to abstract away the differences for
> different architectures.  For example, CMAKE has particular commands
> focused particularly on the way windows libraries work.
>
> Is there a safe forum where we can discuss these issues?

However, that's not going to stop me from suggesting / encouraging /
cajoling / flogging people towards using the more abstract
cross-platform capabilities that CMake provides.  You can write
anything you want in CMake with an ADD_CUSTOM_COMMAND.  Stuff that
only works on a Unix shell, stuff that only works for certain
toolchains, you name it you can do it.  CMake is a general purpose
language and it doesn't tie your hands as far as rolling your own.
But doing so is often *missing the point*.  CMake is supposed to be
doing certain things for you, that's why you're using a build system.
The management of AR probably falls within that purview.  And if it
doesn't, it should be made to.


Cheers,
Brandon Van Every