Sorry for my late weigh in on this one, but there are instances where this
would be useful.
E.g. redistro-ing libMyOneLargeLib.a which may be comprised of several other
smaller libs.
Basically I would like to build once, and pass the .o's into MyOneLargeLib.
My only other alternative to add a c
On Friday 21 May 2010, Christoph Rüdiger wrote:
> Am 20.05.2010 um 13:33 schrieb Michael Hertling:
> > On 05/20/2010 01:04 PM, "Christoph Rüdiger" wrote:
> >> [...]
> >> I've a directory src containing the complete source code of the
> >> program and
> >> another directory called test containing th
On 05/21/2010 03:05 PM, Christoph Rüdiger wrote:
> Am 20.05.2010 um 13:33 schrieb Michael Hertling:
>
>> On 05/20/2010 01:04 PM, "Christoph Rüdiger" wrote:
>>> [...]
>>> I've a directory src containing the complete source code of the
>>> program and
>>> another directory called test containing t
Am 20.05.2010 um 13:33 schrieb Michael Hertling:
On 05/20/2010 01:04 PM, "Christoph Rüdiger" wrote:
[...]
I've a directory src containing the complete source code of the
program and
another directory called test containing the source code for the
unit tests.
In the top level directory is a
On 05/20/2010 01:04 PM, "Christoph Rüdiger" wrote:
> Hi!
>
> I'm new to cmake and couldn't find a solution for my problem:
>
> I've a directory src containing the complete source code of the program and
> another directory called test containing the source code for the unit tests.
> In the top le
Hi!
I'm new to cmake and couldn't find a solution for my problem:
I've a directory src containing the complete source code of the program and
another directory called test containing the source code for the unit tests.
In the top level directory is a CMakeLists.txt that points to the
subdirector