Skip to content
This repository was archived by the owner on Apr 7, 2021. It is now read-only.
This repository was archived by the owner on Apr 7, 2021. It is now read-only.

CMake project name and linking #4

@ssoelvsten

Description

@ssoelvsten

I have the following two pet peeves with this CMake integration, which otherwise seems to work flawlessly.

  1. I'm currently implementing a collection of comparable benchmarks of different BDD libraries, so I'm currently writing code for CUDD, BuDDy and Sylvan and at some point maybe others. The project name is bdd, which is quite generic, which luckily does not create any conflicts, but I see no reason to begin asking for trouble.

    I cannot do as follows

    add_subdirectory (external/BuDDy buddy)
    

    and then

    target_link_libraries(buddy_queens buddy)
    

    but have to use bdd rather than buddy.

  2. I'm furthermore puzzled by the need to directly link to the source code folder for BuDDy rather than everything is taken care of by the add_subdirectory call. Instead to compile an example I have to do

    add_executable(buddy_queens buddy_queens.cpp)
    target_include_directories(buddy_queens PRIVATE ../external/BuDDy/src)
    target_link_libraries(buddy_queens bdd)
    

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions