Unable to statically link in windows via CMake

[wirepair]

I've been fighting with getting libsodium to build statically for windows (fine in linux) for the past few days and am at my wits end.
I'm using the recommended method of using facebook's Findsodium.cmake.

Here's my cmake settings:

set(sodium_USE_STATIC_LIBS ON)
if (WIN32)
  set(sodium_DIR ${CMAKE_SOURCE_DIR}/third_party/libsodium-1.0.18/)
  set(sodium_INCLUDE_DIR ${CMAKE_SOURCE_DIR}/third_party/libsodium-1.0.18/src/libsodium/include/)
  set(sodium_LIBRARY_DEBUG ${CMAKE_SOURCE_DIR}/third_party/libsodium-1.0.18/Build/Debug/x64/libsodium.lib)
  set(sodium_LIBRARY_RELEASE ${CMAKE_SOURCE_DIR}/third_party/libsodium-1.0.18/Build/Release/x64/libsodium.lib)
  link_directories(${sodium_LIBRARY_DIRS})
endif()

find_package(sodium REQUIRED)
target_compile_definitions(sodium INTERFACE SODIUM_STATIC=1)
target_compile_definitions(sodium INTERFACE SODIUM_EXPORT=)

I've gone ahead and built all libsodium in visual studio prior to running my cmake command but I consistently get:
error LNK2019: unresolved external symbol __imp_crypto_aead_xchacha20poly1305_ietf_encrypt referenced in function errors for every libsodium call.

Does anyone know what I'm doing wrong here? Is there an example project that I can look at? Would love some assistance!
Thanks!

[wirepair]

I figured out my problem. I was calling libsodium from a library I built as part of the cmake, but that library did not link against libsodium, only the application that was linking to the library did, hence it was unable to find the symbols.

so top level cmake (as listed above) was fine, but in my library src directory i needed to add:

before:
...
target_link_libraries(pmo_library PRIVATE flecs fmt::fmt flatbuffers)
...
after:
...
target_link_libraries(pmo_library PRIVATE sodium flecs fmt::fmt flatbuffers)
...