Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of absolute paths in some generated CMake files #49

Open
agarny opened this issue Jan 12, 2022 · 1 comment
Open

Use of absolute paths in some generated CMake files #49

agarny opened this issue Jan 12, 2022 · 1 comment

Comments

@agarny
Copy link
Contributor

agarny commented Jan 12, 2022

libCombine shows the same issue as the one described in NuML/NuML#24. In addition, I found that if I pass a target for the zipper library then in Combine-static-config-release.cmake, IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE shows /some/absolute/path/my_zipper_target rather than simply my_zipper_target, but that might be something that I have done wrong... although it works fine for zlib (i.e. I see my_zlib_target and not /some/absolute/path/my_zlib_target). I haven't checked, but could it be that LIBZ_LIBRARY and ZIPPER_LIBRARY are handled differently?

@agarny
Copy link
Contributor Author

agarny commented Jan 12, 2022

I take it back when it comes to my_zlib_target. I have the same problem as with my_zipper_target and (I believe that) it's my problem, not that of libCombine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant