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
Is it possible that there is missing something that allows to find BCL::NodeJSSocket when rerunning configuration step for sapfor in a dev container?
I get this at the beginning of the command, but the autodetection of clang features continue either way, but the configure step fails, and can't continue building.
root ➜ /workspaces/sapfor/build (download-cmake) $ cmake .. -C ../CMakeCache.in -DPTS_EXECUTABLE=/repo/pts/bin/pts.pl -DLLVM_PROJECT_DIR=/workspaces/root/llvm-project -DBUILD_LINK=ON -DBUILD_CLANG=ON -DBUILD_PROFILE=ON -DBCL_NODEJS_SOCKET=ON
loading initial cache file ../CMakeCache.in
-- Perl version: 5.30.0
CMake Error at build/bcl/bcl/BCLConfig.cmake:54 (get_property):
get_property could not find TARGET BCL::NodeJSSocket. Perhaps it has not
yet been created.
Call Stack (most recent call first):
analyzers/tsar/CMakeLists.txt:47 (find_package)
I'm not an expert with CMake yet, but I understand from the file bcl/cmake/BCLConfig.cmake.in near lines 54-55 that the target BCL::NodeJSSocket does not seem to be defined like in the "else" branch of the same if.
If I add add_library(BCL::NodeJSSocket ALIAS NodeJSSocket) just before get_property(BCL_NODEJS_SOCKET_SOURCES TARGET BCL::NodeJSSocket PROPERTY INTERFACE_SOURCES)
like so:
# List of sources from NodeJSSocket (if NodeJSSocket is available).if(BCL_NODEJS_SOCKET)
add_library(BCL::NodeJSSocket ALIAS NodeJSSocket)
get_property(BCL_NODEJS_SOCKET_SOURCES TARGET BCL::NodeJSSocket
PROPERTY INTERFACE_SOURCES)
endif()
I seem to be able to get past that configure error, and I'm still waiting to finish building.
Is it a real solution, or does it have some undesired effects?
The text was updated successfully, but these errors were encountered:
Is it possible that there is missing something that allows to find
BCL::NodeJSSocket
when rerunning configuration step for sapfor in a dev container?I get this at the beginning of the command, but the autodetection of clang features continue either way, but the configure step fails, and can't continue building.
I'm not an expert with CMake yet, but I understand from the file
bcl/cmake/BCLConfig.cmake.in
near lines 54-55 that the targetBCL::NodeJSSocket
does not seem to be defined like in the "else" branch of the same if.bcl/cmake/BCLConfig.cmake.in
Lines 54 to 55 in 028188e
At lines 64-66, there is an alias that defines
BCL::NodeJSSocket
bcl/cmake/BCLConfig.cmake.in
Lines 64 to 66 in 028188e
bcl/cmake/BCLConfig.cmake.in
Lines 43 to 79 in 028188e
If I add
add_library(BCL::NodeJSSocket ALIAS NodeJSSocket)
just beforeget_property(BCL_NODEJS_SOCKET_SOURCES TARGET BCL::NodeJSSocket PROPERTY INTERFACE_SOURCES)
like so:
I seem to be able to get past that configure error, and I'm still waiting to finish building.
Is it a real solution, or does it have some undesired effects?
The text was updated successfully, but these errors were encountered: