2013-06-06 01:53:30 +02:00
|
|
|
################################################################################
|
2013-01-20 10:22:32 +01:00
|
|
|
#
|
|
|
|
|
# cmake
|
|
|
|
|
#
|
2013-06-06 01:53:30 +02:00
|
|
|
################################################################################
|
2013-01-20 10:22:32 +01:00
|
|
|
|
2017-02-28 19:07:23 +01:00
|
|
|
CMAKE_VERSION_MAJOR = 3.7
|
2017-02-28 19:07:26 +01:00
|
|
|
CMAKE_VERSION = $(CMAKE_VERSION_MAJOR).2
|
2016-01-28 21:01:25 +01:00
|
|
|
CMAKE_SITE = https://cmake.org/files/v$(CMAKE_VERSION_MAJOR)
|
2017-03-30 15:43:38 +02:00
|
|
|
CMAKE_LICENSE = BSD-3-Clause
|
2013-01-20 10:22:32 +01:00
|
|
|
CMAKE_LICENSE_FILES = Copyright.txt
|
2010-03-02 22:31:26 +01:00
|
|
|
|
2016-07-01 17:53:29 +02:00
|
|
|
# CMake is a particular package:
|
|
|
|
|
# * CMake can be built using the generic infrastructure or the cmake one.
|
|
|
|
|
# Since Buildroot has no requirement regarding the host system cmake
|
|
|
|
|
# program presence, it uses the generic infrastructure to build the
|
|
|
|
|
# host-cmake package, then the (target-)cmake package can be built
|
|
|
|
|
# using the cmake infrastructure;
|
|
|
|
|
# * CMake bundles its dependencies within its sources. This is the
|
|
|
|
|
# reason why the host-cmake package has no dependencies:, whereas
|
|
|
|
|
# the (target-)cmake package has a lot of dependencies, using only
|
|
|
|
|
# the system-wide libraries instead of rebuilding and statically
|
|
|
|
|
# linking with the ones bundled into the CMake sources.
|
|
|
|
|
|
2017-02-28 19:07:23 +01:00
|
|
|
CMAKE_DEPENDENCIES = zlib jsoncpp libcurl libarchive expat bzip2 xz libuv
|
2015-03-08 10:47:20 +01:00
|
|
|
|
|
|
|
|
CMAKE_CONF_OPTS = \
|
2015-03-30 23:07:30 +02:00
|
|
|
-DKWSYS_LFS_WORKS=TRUE \
|
2015-03-08 10:47:20 +01:00
|
|
|
-DKWSYS_CHAR_IS_SIGNED=TRUE \
|
|
|
|
|
-DCMAKE_USE_SYSTEM_LIBRARIES=1 \
|
|
|
|
|
-DCTEST_USE_XMLRPC=OFF \
|
|
|
|
|
-DBUILD_CursesDialog=OFF
|
2014-08-31 21:55:14 +02:00
|
|
|
|
2015-03-07 09:27:55 +01:00
|
|
|
# Get rid of -I* options from $(HOST_CPPFLAGS) to prevent that a
|
|
|
|
|
# header available in $(HOST_DIR)/usr/include is used instead of a
|
|
|
|
|
# CMake internal header, e.g. lzma* headers of the xz package
|
|
|
|
|
HOST_CMAKE_CFLAGS = $(shell echo $(HOST_CFLAGS) | sed -r "s%$(HOST_CPPFLAGS)%%")
|
|
|
|
|
HOST_CMAKE_CXXFLAGS = $(shell echo $(HOST_CXXFLAGS) | sed -r "s%$(HOST_CPPFLAGS)%%")
|
|
|
|
|
|
2010-03-02 22:31:26 +01:00
|
|
|
define HOST_CMAKE_CONFIGURE_CMDS
|
2013-03-06 08:14:22 +01:00
|
|
|
(cd $(@D); \
|
cmake: pass HOST_CONFIGURE_OPTS at configure time
Since we bumped CMake from 3.5.2 to 3.6.3 in commit
99ed85d74081a8611a6f6d1f3d745a5c40aef975, CMake uses pkg-config during
its configure step to find available libraries on the host.
If host-pkgconf was not built before host-cmake, everything was working
fine. However, if host-pkgconf was built before, the configure step of
host-cmake was finding pkg-config and used it to find
libraries. Unfortunately, since we were not passing
PKG_CONFIG_PATH/PKG_CONFIG_SYSROOT_DIR, pkg-config was behaving in its
"default" mode, i.e returning results valid when building things for the
target, not for the host. This lead to header paths pointing to the
staging directory being used when building native binary objects,
causing all sort of build failures.
This commit fixes that by passing $(HOST_CONFIGURE_OPTS) to the
environment of host-cmake configure step. This variable contains
HOST_MAKE_ENV, which itself contains the appropriate
PKG_CONFIG_PATH/PKG_CONFIG_SYSROOT_DIR definitions.
At the same time, we drop LDFLAGS="$(HOST_LDFLAGS)" because this
definition is already in $(HOST_CONFIGURE_OPTS).
Fixes:
http://autobuild.buildroot.net/results/4e703ed8c2eb0f914794038b0ef7bd73a67f38ce/
(and 424 similar build failures)
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-03 16:24:23 +01:00
|
|
|
$(HOST_CONFIGURE_OPTS) \
|
2015-03-07 09:27:55 +01:00
|
|
|
CFLAGS="$(HOST_CMAKE_CFLAGS)" \
|
cmake: forward HOST_{C, LD}FLAGS as cmake flags
During the CMake bootstrap phase, the {C,LD}FLAGS set in the bootstrap
environment are not forwarded/converted as CMake flags.
The CMake build contains a bootstrap phase building a minimal CMake
program using a standard Makfile, then reconfigures itself with this
minimal program.
On system with no ncurses installed, and because the prefix option
points to $(HOST_DIR)/usr, if host-cmake was built after host-ncurses,
then ncurses libraries and headers are correctly found (in the host
tree) during the second configuration (because of the prefix). However,
it fails at building ccmake (the curses interface) because the
CMAKE_C_FLAGS, CMAKE_CXX_FLAGS and CMAKE_EXE_LINKER_FLAGS do not
point to the host tree.
Because these flags are needed when running the bootstrap script,
this patch makes sure the same flags are set when running the second
configuration.
Reported-by: Fabio Porcedda <fabio.porcedda@gmail.com>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Cc: Fabio Porcedda <fabio.porcedda@gmail.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-09 11:07:27 +02:00
|
|
|
./bootstrap --prefix=$(HOST_DIR)/usr \
|
|
|
|
|
--parallel=$(PARALLEL_JOBS) -- \
|
2015-03-07 09:27:55 +01:00
|
|
|
-DCMAKE_C_FLAGS="$(HOST_CMAKE_CFLAGS)" \
|
|
|
|
|
-DCMAKE_CXX_FLAGS="$(HOST_CMAKE_CXXFLAGS)" \
|
cmake: forward HOST_{C, LD}FLAGS as cmake flags
During the CMake bootstrap phase, the {C,LD}FLAGS set in the bootstrap
environment are not forwarded/converted as CMake flags.
The CMake build contains a bootstrap phase building a minimal CMake
program using a standard Makfile, then reconfigures itself with this
minimal program.
On system with no ncurses installed, and because the prefix option
points to $(HOST_DIR)/usr, if host-cmake was built after host-ncurses,
then ncurses libraries and headers are correctly found (in the host
tree) during the second configuration (because of the prefix). However,
it fails at building ccmake (the curses interface) because the
CMAKE_C_FLAGS, CMAKE_CXX_FLAGS and CMAKE_EXE_LINKER_FLAGS do not
point to the host tree.
Because these flags are needed when running the bootstrap script,
this patch makes sure the same flags are set when running the second
configuration.
Reported-by: Fabio Porcedda <fabio.porcedda@gmail.com>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Cc: Fabio Porcedda <fabio.porcedda@gmail.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-09 11:07:27 +02:00
|
|
|
-DCMAKE_EXE_LINKER_FLAGS="$(HOST_LDFLAGS)" \
|
2014-05-12 13:19:36 +02:00
|
|
|
-DBUILD_CursesDialog=OFF \
|
2013-03-06 08:14:22 +01:00
|
|
|
)
|
2010-03-02 22:31:26 +01:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define HOST_CMAKE_BUILD_CMDS
|
2013-03-06 08:14:22 +01:00
|
|
|
$(HOST_MAKE_ENV) $(MAKE) -C $(@D)
|
2010-03-02 22:31:26 +01:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define HOST_CMAKE_INSTALL_CMDS
|
2015-04-23 21:46:13 +02:00
|
|
|
$(HOST_MAKE_ENV) $(MAKE) -C $(@D) install/fast
|
2010-03-02 22:31:26 +01:00
|
|
|
endef
|
|
|
|
|
|
2015-03-08 10:47:20 +01:00
|
|
|
define CMAKE_REMOVE_EXTRA_DATA
|
|
|
|
|
rm $(TARGET_DIR)/usr/bin/{cmake,cpack}
|
|
|
|
|
rm -fr $(TARGET_DIR)/usr/share/cmake-$(CMAKE_VERSION_MAJOR)/{completions,editors}
|
|
|
|
|
rm -fr $(TARGET_DIR)/usr/share/cmake-$(CMAKE_VERSION_MAJOR)/{Help,include}
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define CMAKE_INSTALL_CTEST_CFG_FILE
|
|
|
|
|
$(INSTALL) -m 0644 -D $(@D)/Modules/CMake.cmake \
|
|
|
|
|
$(TARGET_DIR)/usr/share/cmake-$(CMAKE_VERSION_MAJOR)/Modules/CMake.cmake.ctest
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
CMAKE_POST_INSTALL_TARGET_HOOKS += CMAKE_REMOVE_EXTRA_DATA
|
|
|
|
|
CMAKE_POST_INSTALL_TARGET_HOOKS += CMAKE_INSTALL_CTEST_CFG_FILE
|
|
|
|
|
|
|
|
|
|
define CMAKE_INSTALL_TARGET_CMDS
|
|
|
|
|
(cd $(@D); \
|
|
|
|
|
$(HOST_MAKE_ENV) DESTDIR=$(TARGET_DIR) \
|
|
|
|
|
cmake -P cmake_install.cmake \
|
|
|
|
|
)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
$(eval $(cmake-package))
|
2012-07-03 00:06:54 +02:00
|
|
|
$(eval $(host-generic-package))
|
