Unified Automation Forum

When building the cpp bundle, the libuastack.so is built to the lib folder, whereas the other libs are built to lib64.

However, libuastack.so is built for 64-bit:
$ file build_optimized/install_path/lib/libuastack.so
build_optimized/install_path/lib/libuastack.so: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=b6f1b324483629f84e61b2fb9f8dc8e69a748359, with debug_info, not stripped

.../uastack/CMakeLists.txt contains:
...
install(TARGETS ${PROJECT_NAME}
RUNTIME DESTINATION bin
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib
...

The CMakeLists.txt files from the other libraries (i.e. uabasecpp) contain:
...
install(TARGETS ${PROJECT_NAME}
RUNTIME DESTINATION bin
LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}
...

Shouldn't the uastack/CMakeLists.txt file be adjusted to also use ${CMAKE_INSTALL_LIBDIR}?
Or is there another reason that we should be aware of why libuastack.so is in lib instead of lib64?