Bug:Boost: Use shlibs instead of header-only for call_stack::top_

This symbol is defined as a static member object inside of a
boost detail header. When boost headers are used in a project
that uses Boost in both the main binary as well as dlopen()'d
shlibs, the top_ symbol gets duplicated and the metadata gets
partitioned.

We use the Boost shlib to unify both the main binary and the
shlibs to use the same memory address for top_.

This involves marking the templated object call_stack::top_ as
"extern" and then declaring to Boost that we intend to use the
shlibs.

commonLibs/livoxProto1/CMakeLists.txt

@@ -13,7 +13,14 @@ if(ENABLE_LIB_livoxProto1)
 	# Set config define for header generation
 	add_compile_definitions(CONFIG_LIB_LIVOXPROTO1_ENABLED)
 	target_include_directories(livoxProto1 PUBLIC ${Boost_INCLUDE_DIRS})
-	target_link_libraries(livoxProto1 ${Boost_LIBRARIES})
+	target_link_libraries(livoxProto1 PUBLIC Boost::system Boost::log)
+
+	# Verify Boost dynamic dependencies after build
+	add_custom_command(TARGET livoxProto1 POST_BUILD
+		COMMAND ${CMAKE_COMMAND} -DVERIFY_FILE="$<TARGET_FILE:livoxProto1>"
+			-P ${CMAKE_SOURCE_DIR}/cmake/VerifyBoostDynamic.cmake
+		COMMENT "Verifying Boost dynamic dependencies for livoxProto1"
+	)
 
 	# Install rules
 	install(TARGETS livoxProto1 DESTINATION lib)