You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2021. It is now read-only.
I have the following two pet peeves with this CMake integration, which otherwise seems to work flawlessly.
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.
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
I have the following two pet peeves with this CMake integration, which otherwise seems to work flawlessly.
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
and then
but have to use
bdd
rather thanbuddy
.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 doThe text was updated successfully, but these errors were encountered: