secure-software-engineering / phasar

A LLVM-based static analysis framework.
Other
933 stars 140 forks source link

CMake Error: install TARGETS given no LIBRARY DESTINATION for shared library target #599

Closed boehmseb closed 1 year ago

boehmseb commented 1 year ago

While cleaning up the phasar integration into the VaRA-Tool-Suite (https://github.com/se-sic/VaRA-Tool-Suite/pull/664) I got the following CMake error basically for all phasar libraries:

CMake Error at cmake/phasar_macros.cmake:239 (install):                                                                                                                                                                                 
  install TARGETS given no LIBRARY DESTINATION for shared library target                                                                                                                                                                
  "phasar_analysis_strategy".                                                                                                                                                                                                           
Call Stack (most recent call first):                                                                                                                                                                                                    
  lib/AnalysisStrategy/CMakeLists.txt:13 (add_phasar_library)

It seems like 9c39fd872c7a78a18f73260c56ffd6e95061d4c6 could be the culprit.

fabianbs96 commented 1 year ago

Hi @boehmseb, that looks quite strange. On my private system I could not reproduce that error -- that is, vara-buildsetup init phasar; vara-buildsetup build phasar complete successfully; actually include(GNUInstallDirs) from out top-level CMakeLists.txt should already set all these required paths correctly. I will investigate further

boehmseb commented 1 year ago

Reproducing should be possible with vara-buildsetup build phasar --container=DEBIAN_10.

MMory commented 1 year ago

should be fixed with recent merge of #602, please confirm @boehmseb

boehmseb commented 1 year ago

Yes, can confirm.