Skip to content

Conversation

@Bill-hbrhbr
Copy link
Collaborator

@Bill-hbrhbr Bill-hbrhbr commented Mar 25, 2025

Description

For header-only libraries, we add the target using add_library(${arg_cpp_lib_NAME} INTERFACE) call, making it an interface target. For interface targets, doing the following will fail

target_link_libraries(
    ${arg_cpp_lib_NAME}
    PUBLIC
        ${arg_cpp_lib_PUBLIC_LINK_LIBRARIES}
    PRIVATE
        ${arg_cpp_lib_PRIVATE_LINK_LIBRARIES}
)

as interface targets can only have INTERFACE properties.
Instead of adding a new arg called INTERFACE_LINK_LIBRARIES to cpp_library(), we keep using PUBLIC_LINK_LIBRARIES:

target_link_libraries(
    ${arg_cpp_lib_NAME}
    INTERFACE
        ${arg_cpp_lib_PUBLIC_LINK_LIBRARIES}
)

and forbids users from specifying PRIVATE_LINK_LIBRARIES as interface dependencies will get propagated.

Checklist

  • The PR satisfies the contribution guidelines.
  • This is a breaking change and that has been indicated in the PR title, OR this isn't a
    breaking change.
  • Necessary docs have been updated, OR no docs need to be updated.

Validation performed

  • Cmake helper function fix. Targets compile successfully as usual.

@Bill-hbrhbr Bill-hbrhbr requested a review from a team as a code owner March 25, 2025 05:45
@coderabbitai
Copy link

coderabbitai bot commented Mar 25, 2025

Walkthrough

This PR refines the linking logic within the cpp_library function in the CMake helper file. It adds error handling for cases when a header-only library incorrectly specifies private link libraries, raising a fatal error. Additionally, the PR restructures the linking commands by explicitly linking public libraries as INTERFACE libraries for header-only libraries and moving the general linking commands into the non-header-only branch.

Changes

File Summary
CMake/ystdlib-cpp-helpers.cmake - Added error handling: Checks if arg_cpp_lib_PRIVATE_LINK_LIBRARIES is defined for header-only libraries and issues a fatal error if yes.
- Modified linking logic: Links public libraries as INTERFACE libraries for header-only libraries; moved linking commands for non-header-only libraries into an else branch.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant CMakeFunction as cpp_library()

    Caller->>CMakeFunction: Invoke cpp_library()
    alt Header-only library?
        CMakeFunction->>CMakeFunction: Check if arg_cpp_lib_PRIVATE_LINK_LIBRARIES is defined
        alt Private libraries defined?
            CMakeFunction->>Caller: Emit fatal error
        else
            CMakeFunction->>Caller: Link public libraries as INTERFACE
        end
    else Non-header-only library
        CMakeFunction->>Caller: Execute linking in else branch
    end
Loading

Possibly related PRs

Suggested reviewers

  • davidlion

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
CMake/ystdlib-cpp-helpers.cmake (1)

68-98: Consider adding explanatory comments for future maintainers

While the code changes are technically correct, it might be helpful to add comments explaining why header-only libraries can only use INTERFACE linking. This would benefit developers who aren't familiar with CMake's library types.

 if(_IS_INTERFACE_LIB)
+    # Header-only libraries must use INTERFACE linkage as they don't have a compiled component
     if(arg_cpp_lib_PRIVATE_LINK_LIBRARIES)
         message(
             FATAL_ERROR
             "`PRIVATE_LINK_LIBRARIES` disabled for header-only library ${_ALIAS_TARGET_NAME}."
         )
     endif()
     add_library(${arg_cpp_lib_NAME} INTERFACE)
     target_link_libraries(${arg_cpp_lib_NAME} INTERFACE ${arg_cpp_lib_PUBLIC_LINK_LIBRARIES})
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6aac241 and 990f4e8.

📒 Files selected for processing (1)
  • CMake/ystdlib-cpp-helpers.cmake (2 hunks)
🔇 Additional comments (3)
CMake/ystdlib-cpp-helpers.cmake (3)

68-73: Strong error handling for header-only libraries

This is a good addition that prevents misuse of the PRIVATE_LINK_LIBRARIES parameter with header-only libraries. Since header-only libraries are implemented as CMake INTERFACE libraries, they can't have private linkage (as there's no compiled artifact). The error message clearly explains the issue to users.


75-75: Appropriate linking of public dependencies for header-only libraries

This change correctly uses the INTERFACE keyword for linking public dependencies to header-only libraries, which ensures that consumers of the library will inherit these dependencies.


92-98: Proper organization of linking commands for non-header-only libraries

Moving the linking commands for both public and private libraries into the non-header-only branch is appropriate. This ensures the correct linking visibility is used based on library type.

@Bill-hbrhbr Bill-hbrhbr changed the title fix(cmake): Fix dependency linking for header-only libraries. fix(cmake): Correct linking of dependencies for interface (header-only) libraries Mar 25, 2025
@davidlion davidlion changed the title fix(cmake): Correct linking of dependencies for interface (header-only) libraries fix(cmake): Correct linking of dependencies for interface (header-only) libraries. Mar 25, 2025
@Bill-hbrhbr Bill-hbrhbr merged commit 8090ca6 into y-scope:main Mar 25, 2025
14 checks passed
@Bill-hbrhbr Bill-hbrhbr deleted the fix-header-only-lib-linkage branch March 25, 2025 20:36
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

Successfully merging this pull request may close these issues.

2 participants