|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #59373] [MXE] for dependencies that use cmake, don't build static libraries |
Date: | Thu, 29 Oct 2020 10:29:29 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36 Edg/86.0.622.56 |
Follow-up Comment #15, bug #59373 (project octave): It is quite possible that BUILD_STATIC_LIBS is a variable that just "happens" to be used by many packages. I saw ONLY_SHARED_LIBS in the CMakeLists.txt file of hdf5. Its description is "Only Build Shared Libraries". So I figured this is probably what we want. (Given that I'm still struggling to correctly interpret the messages about BUILD_STATIC_LIBS and BUILD_SHARED_LIBS.) I don't remember having seen that particular variable in other CMakeLists.txt files. But tbh, I didn't focus on that then. It's probably because I'm no native speaker, so please correct me if my interpretation is wrong. But what I gather from `./usr/bin/cmake --help-policy CMP0077` is: The OLD behavior (which currently is used) ignores the value we set for e.g. BUILD_STATIC_LIBS. Instead a new (cached) variable is created that has the value defined in the subproject. The NEW behavior (which could be activated by a policy) lets our value override the value set by the subproject. If that is the case (fall back to OLD behavior), why do we see a change in behavior? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59373> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |