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

**URL:** https://discourse.cmake.org/t/cmake-install-make-install-ninja-install-doesnt-install-dependencies/13079
**Category:** Code
**Tags:** os:linux, gen:makefiles, gen:ninja
**Created:** [November 27, 2024, 5:35pm UTC](https://discourse.cmake.org/t/cmake-install-make-install-ninja-install-doesnt-install-dependencies/13079 "2024-11-27T17:35:44Z")
**Posts on this page:** 1
**Showing post:** 23

<div class="post-metadata">

### Author: ![ClausKlein](https://discourse.cmake.org/user_avatar/discourse.cmake.org/clausklein/32/352_2.png) [@ClausKlein](https://discourse.cmake.org/u/ClausKlein)
#### Post date: [December 15, 2024, 11:34pm UTC](https://discourse.cmake.org/t/cmake-install-make-install-ninja-install-doesnt-install-dependencies/13079/23 "2024-12-15T23:34:03Z")

</div>

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

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

> <https://github.com/ClausKlein/openssl-cmake/blob/master/CMakeLists.txt>

#### small problems are caused by cmake:

- [What controls the use of lib64 as CMAKE\_INSTALL\_LIBDIR?](https://discourse.cmake.org/t/what-controls-the-use-of-lib64-as-cmake-install-libdir/13212)

### others caused Good Good by MSVC:

- [How to control the MSVC CRT with cmake?](https://discourse.cmake.org/t/how-to-control-the-msvc-crt-with-cmake/13195)

## But there are real problems with openssl itself:

- [Error: Imported target "OpenSSL::Crypto" includes non-existent path · Issue #26185 · openssl/openssl · GitHub](https://github.com/openssl/openssl/issues/26185)
- [The exported cmake config package should contain a OpenSSLConfig-targets-release.cmake file · Issue #26179 · openssl/openssl · GitHub](https://github.com/openssl/openssl/issues/26179)

---

_[View the full topic](https://discourse.cmake.org/t/cmake-install-make-install-ninja-install-doesnt-install-dependencies/13079)._