Cmake how to avoid transitive linking of Target after policy cmp0022 set to new
up vote
0
down vote
favorite
I have library libB
linked to libA
using target_link_libraries(libA Interface libB)
.This libA
is then linked to another libC
like target_link_libraries(libC libA)
.
Now if my understanding is correct then if the cmp0022
is set to new
then libC
is transitively linked to both A
and B
, but I don't want it to happen for some targets as while building I'm getting some unresolved symbols error.
These errors are from targets that are transitively linked. How can it be solved?
Setting the policy back to old is not an option. Also linking the library as private is also not accepted as this issue is only for some targets. I tried getting the value of INTERFACE_LINK_LIBRARIES
but is showing only those libraries that are directly linked not the one transitively linked. In which cmake
property I can get this?
cmake
add a comment |
up vote
0
down vote
favorite
I have library libB
linked to libA
using target_link_libraries(libA Interface libB)
.This libA
is then linked to another libC
like target_link_libraries(libC libA)
.
Now if my understanding is correct then if the cmp0022
is set to new
then libC
is transitively linked to both A
and B
, but I don't want it to happen for some targets as while building I'm getting some unresolved symbols error.
These errors are from targets that are transitively linked. How can it be solved?
Setting the policy back to old is not an option. Also linking the library as private is also not accepted as this issue is only for some targets. I tried getting the value of INTERFACE_LINK_LIBRARIES
but is showing only those libraries that are directly linked not the one transitively linked. In which cmake
property I can get this?
cmake
Linking with additional library cannot be source of "undefined reference" error. So your problem is somewhere else. Also, the policy CMP0022 is not about INTERFACE linking in whole, it is about configuration-specific interface linking.
– Tsyvarev
Nov 21 at 21:14
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have library libB
linked to libA
using target_link_libraries(libA Interface libB)
.This libA
is then linked to another libC
like target_link_libraries(libC libA)
.
Now if my understanding is correct then if the cmp0022
is set to new
then libC
is transitively linked to both A
and B
, but I don't want it to happen for some targets as while building I'm getting some unresolved symbols error.
These errors are from targets that are transitively linked. How can it be solved?
Setting the policy back to old is not an option. Also linking the library as private is also not accepted as this issue is only for some targets. I tried getting the value of INTERFACE_LINK_LIBRARIES
but is showing only those libraries that are directly linked not the one transitively linked. In which cmake
property I can get this?
cmake
I have library libB
linked to libA
using target_link_libraries(libA Interface libB)
.This libA
is then linked to another libC
like target_link_libraries(libC libA)
.
Now if my understanding is correct then if the cmp0022
is set to new
then libC
is transitively linked to both A
and B
, but I don't want it to happen for some targets as while building I'm getting some unresolved symbols error.
These errors are from targets that are transitively linked. How can it be solved?
Setting the policy back to old is not an option. Also linking the library as private is also not accepted as this issue is only for some targets. I tried getting the value of INTERFACE_LINK_LIBRARIES
but is showing only those libraries that are directly linked not the one transitively linked. In which cmake
property I can get this?
cmake
cmake
edited Nov 21 at 21:09
Daniel
1,48511228
1,48511228
asked Nov 21 at 16:29
Malu
1
1
Linking with additional library cannot be source of "undefined reference" error. So your problem is somewhere else. Also, the policy CMP0022 is not about INTERFACE linking in whole, it is about configuration-specific interface linking.
– Tsyvarev
Nov 21 at 21:14
add a comment |
Linking with additional library cannot be source of "undefined reference" error. So your problem is somewhere else. Also, the policy CMP0022 is not about INTERFACE linking in whole, it is about configuration-specific interface linking.
– Tsyvarev
Nov 21 at 21:14
Linking with additional library cannot be source of "undefined reference" error. So your problem is somewhere else. Also, the policy CMP0022 is not about INTERFACE linking in whole, it is about configuration-specific interface linking.
– Tsyvarev
Nov 21 at 21:14
Linking with additional library cannot be source of "undefined reference" error. So your problem is somewhere else. Also, the policy CMP0022 is not about INTERFACE linking in whole, it is about configuration-specific interface linking.
– Tsyvarev
Nov 21 at 21:14
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53416530%2fcmake-how-to-avoid-transitive-linking-of-target-after-policy-cmp0022-set-to-new%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Linking with additional library cannot be source of "undefined reference" error. So your problem is somewhere else. Also, the policy CMP0022 is not about INTERFACE linking in whole, it is about configuration-specific interface linking.
– Tsyvarev
Nov 21 at 21:14