On 09/13/2011 11:05 AM, Michael Wild wrote:
> On 09/12/2011 09:06 PM, Erik Johansson wrote:
>> On Mon, Sep 12, 2011 at 20:30, Michael Wild wrote:
>>> How about using a custom command that runs the unit test using a
>>> wrapper script that upon successful completion creates a stamp-file and
>>> dep
On 09/12/2011 09:06 PM, Erik Johansson wrote:
> On Mon, Sep 12, 2011 at 20:30, Michael Wild wrote:
>> How about using a custom command that runs the unit test using a
>> wrapper script that upon successful completion creates a stamp-file and
>> depends upon the unit-test executable target itself?
On Mon, Sep 12, 2011 at 20:30, Michael Wild wrote:
> How about using a custom command that runs the unit test using a
> wrapper script that upon successful completion creates a stamp-file and
> depends upon the unit-test executable target itself?
This seems to work:
add_executable(unittest ${tes
On Mon 12 Sep 2011 05:47:18 PM CEST, Ben Medina wrote:
> On Sat, Sep 10, 2011 at 9:10 AM, Erik Johansson wrote:
>
>> How does one get cmake to run the unit test as part of the build so that:
>> - If the unit test fails, the build fails.
>> - If the unit test has failed, and make is run again, the
On Sat, Sep 10, 2011 at 9:10 AM, Erik Johansson wrote:
> How does one get cmake to run the unit test as part of the build so that:
> - If the unit test fails, the build fails.
> - If the unit test has failed, and make is run again, the unit test
> will run again.
> - If the unit test has succeede
Hi,
How does one get cmake to run the unit test as part of the build so that:
- If the unit test fails, the build fails.
- If the unit test has failed, and make is run again, the unit test
will run again.
- If the unit test has succeeded, and make is run again, the unit test
will not run again.
I
