From: Jan Heylen <heyleke@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 2/3] pkg-cmake: add note on BUILD_STATIC_LIBS
Date: Wed, 3 Jan 2018 22:20:10 +0100 [thread overview]
Message-ID: <1515014411-3504-3-git-send-email-heyleke@gmail.com> (raw)
In-Reply-To: <1515014411-3504-1-git-send-email-heyleke@gmail.com>
From: Jan Heylen <jan.heylen@nokia.com>
as BUILD_STATIC_LIBS is not a standard cmake variable (while BUILD_SHARED_LIBS is)
we shouldn't add it in pkg-cmake.mk, although for some packages that would
make sense. Therefore, add a note so we don't forget about this abnormality.
see: https://cmake.org/cmake/help/v3.8/manual/cmake-variables.7.html#variables-that-change-behavior
Signed-off-by: Jan Heylen <jan.heylen@nokia.com>
---
package/pkg-cmake.mk | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/package/pkg-cmake.mk b/package/pkg-cmake.mk
index 6739704..b75cb98 100644
--- a/package/pkg-cmake.mk
+++ b/package/pkg-cmake.mk
@@ -80,6 +80,15 @@ ifndef $(2)_CONFIGURE_CMDS
ifeq ($(4),target)
# Configure package for target
+#
+# Note:
+# BUILD_SHARED_LIBS is a cmake internal variable,
+# BUILD_STATIC_LIBS is not standard in any way, which means some
+# projects may choose another name for a similar option and there is not
+# much we can do about this.
+# see: https://cmake.org/cmake/help/v3.8/manual/cmake-variables.7.html#variables-that-change-behavior
+#
+# So: we handle BUILD_SHARED_LIBS here, but BUILD_STATIC_LIBS must be handled per package
define $(2)_CONFIGURE_CMDS
(mkdir -p $$($$(PKG)_BUILDDIR) && \
cd $$($$(PKG)_BUILDDIR) && \
--
2.7.4
next prev parent reply other threads:[~2018-01-03 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 21:20 [Buildroot] [PATCH v5 0/3] Opentracing-cpp: new package Jan Heylen
2018-01-03 21:20 ` [Buildroot] [PATCH v5 1/3] rabbitmq-c: BUILD_SHARED_LIBS is handled in pkg-cmake.mk Jan Heylen
2018-01-03 21:20 ` Jan Heylen [this message]
2018-01-03 21:20 ` [Buildroot] [PATCH v5 3/3] opentracing-cpp: new package Jan Heylen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1515014411-3504-3-git-send-email-heyleke@gmail.com \
--to=heyleke@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox