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

CMake project name and linking #4

Open
SSoelvsten opened this issue Oct 1, 2020 · 1 comment
Open

CMake project name and linking #4

SSoelvsten opened this issue Oct 1, 2020 · 1 comment

Comments

@SSoelvsten
Copy link

SSoelvsten commented Oct 1, 2020

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)
    
@SSoelvsten
Copy link
Author

I do now see, that the choice of bdd is warranted and arguments as for why it should stay. The second I'd still question.

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

No branches or pull requests

1 participant