kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/ExportImport/Export/testLibDepends.c

26 lines
521 B
C
Raw Normal View History

exports: add a test for exporting dependent targets The test exports two libraries into two separate exports, and then include()s the generated export files. This must not fail. Alex
2012-09-23 21:19:55 +04:00
Handle INTERFACE properties transitively for includes and defines. Contextually, the behavior is as if the properties content from another target is included in the string and then the result is evaluated.
2012-09-23 15:45:17 +04:00
#include "testLibIncludeRequired1.h"
#include "testLibIncludeRequired2.h"
#include "testLibIncludeRequired4.h"
#ifndef testLibRequired_IFACE_DEFINE
#error Expected testLibRequired_IFACE_DEFINE
#endif
#ifndef BuildOnly_DEFINE
#error Expected BuildOnly_DEFINE
#endif
#ifdef InstallOnly_DEFINE
#error Unexpected InstallOnly_DEFINE
#endif
exports: add a test for exporting dependent targets The test exports two libraries into two separate exports, and then include()s the generated export files. This must not fail. Alex
2012-09-23 21:19:55 +04:00
extern int testLibRequired(void);
Fix export of STATIC library PRIVATE dependencies with CMP0022 NEW The target_link_libraries command records the PRIVATE dependencies of a STATIC library in INTERFACE_LINK_LIBRARIES as "$<LINK_ONLY:dep>". This hides the target name from export namespacing logic inside a generator expression. When user-written generator expressions reference a target name they must put it inside a "$<TARGET_NAME:dep>" expression to allow the export logic to rename the target. In the case that the private dependency is not already a generator expression, target_link_libraries must use "$<LINK_ONLY:$<TARGET_NAME:dep>>" to allow the export logic to rename the target. Reported-by: Tamás Kenéz <tamas.kenez@gmail.com>
2016-01-15 18:02:52 +03:00
extern int testStaticLibRequiredPrivate(void);
exports: add a test for exporting dependent targets The test exports two libraries into two separate exports, and then include()s the generated export files. This must not fail. Alex
2012-09-23 21:19:55 +04:00
Fix export of STATIC library PRIVATE dependencies with CMP0022 NEW The target_link_libraries command records the PRIVATE dependencies of a STATIC library in INTERFACE_LINK_LIBRARIES as "$<LINK_ONLY:dep>". This hides the target name from export namespacing logic inside a generator expression. When user-written generator expressions reference a target name they must put it inside a "$<TARGET_NAME:dep>" expression to allow the export logic to rename the target. In the case that the private dependency is not already a generator expression, target_link_libraries must use "$<LINK_ONLY:$<TARGET_NAME:dep>>" to allow the export logic to rename the target. Reported-by: Tamás Kenéz <tamas.kenez@gmail.com>
2016-01-15 18:02:52 +03:00
int testLibDepends(void) {
return testLibRequired()
+ testStaticLibRequiredPrivate()
;
}