Hi Nils,
Got It !
As per your suggestion, linked libudev to LLAPI target and rebuilt both LLAPI
lib and App . No errors now .
Thank you !
/Cmake/LLAPI/build$ ldd Source/libLLAPI.so
linux-vdso.so.1 => (0x7ffccff9c000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1
_VERSION_MINOR 4)
-set(CMake_VERSION_PATCH 20151122)
+set(CMake_VERSION_PATCH 20151123)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
You don't. You just assume all relevant targets have already been built by
the time you run the tests... There's no such thing as a test from
an add_test call depending on a target.
There **is** a dependency, of course, if you are using one of the build
products in your test, but it's assumed
Use ALL to include your custom target in the default build of all.
https://cmake.org/cmake/help/v3.4/command/add_custom_target.html
D
On Sunday, November 22, 2015, Nico Schlömer
wrote:
> I was under the impression that if I don't explicitly build a target, it
>
Hi Zac,
In recent versions of CMake (not sure when it was introduced, but it's
available in 3.2.X) you have an extra argument for ExternalProject_Add:
BUILD_BYPRODUCTS.
https://cmake.org/cmake/help/v3.2/module/ExternalProject.html
I use this in a setup very similar to yours to declare all the
Dear CMake developers,
please find attached a small patch that introduces the hinting variable
GLEW_ROOT to FindGLEW.cmake.
Best
Christoph
From c6caa68391010f9fb399d86b1e6ec154d4be3605 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Christoph=20Gr=C3=BCninger?=
Date: Sun, 22 Nov
What do you mean by "depend" in this case? All libs and exes should be
built during a "make" or "make all" or "make install" ... And all that
should be done before any tests get run.
Simply typing "ctest" to execute all the tests never does any building. The
assumed workflow is that you build
I was under the impression that if I don't explicitly build a target, it
won't get build. Perhaps I'm wrong here. In any case, this
```
add_custom_target(convert)
add_dependencies(convert testFetchData)
add_custom_command(
TARGET convert
COMMAND cp test.e test.g
)
```
never gets executed on
The DEPENDS property of a test is meant to ensure test running order in the
case of parallel testing... It simply ensures that one test runs before
another. It is not connected to the build system at all. It's different
than target dependencies.
D
On Sunday, November 22, 2015, David Cole
Aha, this was a misunderstanding of me then. Thanks!
How do I make a test depend on a target then?
Cheers,
Nico
On Sun, Nov 22, 2015 at 8:58 PM David Cole wrote:
> The DEPENDS property of a test is meant to ensure test running order in
> the case of parallel testing... It
Thanks for the hints!
I'm almost there now, the only thing missing is to have my test depend on
the custom_target. This
```
SET_TESTS_PROPERTIES(testname PROPERTIES DEPENDS convert)
```
doesn't do the trick: The target `convert` isn't executed before `ctest`.
Any hints?
Cheers,
Nico
On Sun,
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15855
==
Reported By:Raphael Kubo da Costa
Assigned To:
12 matches
Mail list logo