Skip to content

Use of absolute paths in some generated CMake files #49

@agarny

Description

@agarny

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions