'cmake --install'/'make install'/'ninja install' doesn't install dependencies

ClausKlein · December 15, 2024, 11:34pm

I would use a `toolchain` for `cross compiling`.

An for the unix host build, it would be really simple like here in my example:

CMakeLists.txt

master

cmake_minimum_required(VERSION 3.27...3.31)

project(OpenSSL_ExternalProject LANGUAGES C)

set(BUILD_SHARED_LIBS OFF CACHE BOOL "Forced!" FORCE)

if(NOT CMAKE_C_STANDARD)
    set(CMAKE_C_STANDARD 11)
    set(CMAKE_C_STANDARD_REQUIRED YES)
    set(CMAKE_C_EXTENSIONS NO)
endif()

if(NOT CMAKE_PREFIX_PATH)
    set(CMAKE_PREFIX_PATH ${CMAKE_INSTALL_PREFIX})
endif()

set(CMAKE_SKIP_TEST_ALL_DEPENDENCY NO)
enable_testing()

include(openssl.cmake)

This file has been truncated. show original

small problems are caused by cmake:

What controls the use of lib64 as CMAKE_INSTALL_LIBDIR?

others caused Good Good by MSVC:

How to control the MSVC CRT with cmake?

'cmake --install'/'make install'/'ninja install' doesn't install dependencies

I would use a toolchain for cross compiling.

small problems are caused by cmake:

others caused Good Good by MSVC:

But there are real problems with openssl itself:

I would use a `toolchain` for `cross compiling`.