From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] cmake.bbclass: fix qmake and rpath issues
Date: Tue, 10 May 2011 12:59:15 -0700 [thread overview]
Message-ID: <4DC99913.1060403@linux.intel.com> (raw)
In-Reply-To: <1305039119-1469-1-git-send-email-otavio@ossystems.com.br>
On 05/10/2011 07:51 AM, Otavio Salvador wrote:
> Sync with OE at 3b7d83362027fde4f6850533ab83277d95dda961 however
> without changing the way of generating the toolchain file and making
> it branding agnostic.
>
> Signed-off-by: Otavio Salvador<otavio@ossystems.com.br>
> ---
> meta/classes/cmake.bbclass | 14 ++++++++++++--
> meta/classes/native.bbclass | 4 ++++
> 2 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
> index a4b0c12..011c232 100644
> --- a/meta/classes/cmake.bbclass
> +++ b/meta/classes/cmake.bbclass
> @@ -24,15 +24,18 @@ OECMAKE_CXX_FLAGS ?= "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} ${TARGET_CPPFLAGS} -f
> OECMAKE_C_FLAGS_RELEASE ?= "${SELECTED_OPTIMIZATION} -DNDEBUG"
> OECMAKE_CXX_FLAGS_RELEASE ?= "${SELECTED_OPTIMIZATION} -DNDEBUG"
>
> +OECMAKE_RPATH ?= ""
> +
> cmake_do_generate_toolchain_file() {
> cat> ${WORKDIR}/toolchain.cmake<<EOF
> # CMake system name must be something like "Linux".
> # This is important for cross-compiling.
> set( CMAKE_SYSTEM_NAME `echo ${SDK_OS} | sed 's/^./\u&/'` )
> +set( CMAKE_SYSTEM_PROCESSOR ${TARGET_ARCH} )
> set( CMAKE_C_COMPILER ${OECMAKE_C_COMPILER} )
> set( CMAKE_CXX_COMPILER ${OECMAKE_CXX_COMPILER} )
> -set( CMAKE_C_FLAGS "${OECMAKE_C_FLAGS}" CACHE STRING "poky CFLAGS" )
> -set( CMAKE_CXX_FLAGS "${OECMAKE_CXX_FLAGS}" CACHE STRING "poky CXXFLAGS" )
> +set( CMAKE_C_FLAGS "${OECMAKE_C_FLAGS}" CACHE STRING "CFLAGS" )
> +set( CMAKE_CXX_FLAGS "${OECMAKE_CXX_FLAGS}" CACHE STRING "CXXFLAGS" )
> set( CMAKE_C_FLAGS_RELEASE "${OECMAKE_C_FLAGS_RELEASE}" CACHE STRING "CFLAGS for release" )
> set( CMAKE_CXX_FLAGS_RELEASE "${OECMAKE_CXX_FLAGS_RELEASE}" CACHE STRING "CXXFLAGS for release" )
>
> @@ -43,6 +46,13 @@ set( CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY )
> set( CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY )
> set( CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY )
>
> +# Use qt.conf settings
> +set( ENV{QT_CONF_PATH} ${WORKDIR}/qt.conf )
> +
> +# We need to set the rpath to the correct directory as cmake does not provide any
> +# directory as rpath by default
> +set( CMAKE_INSTALL_RPATH ${OECMAKE_RPATH} )
> +
> # Use native cmake modules
> set( CMAKE_MODULE_PATH ${STAGING_DATADIR}/cmake/Modules/ )
> EOF
> diff --git a/meta/classes/native.bbclass b/meta/classes/native.bbclass
> index d9e67f6..e06f02a 100644
> --- a/meta/classes/native.bbclass
> +++ b/meta/classes/native.bbclass
> @@ -11,6 +11,10 @@ PACKAGES_DYNAMIC = ""
> PACKAGES_DYNAMIC_virtclass-native = ""
> PACKAGE_ARCH = "${BUILD_ARCH}"
>
> +# used by cmake class
> +OECMAKE_RPATH = "${libdir}"
> +OECMAKE_RPATH_virtclass-native = "${libdir}"
> +
In Richard's email he proposed one or the other be set, why do you need
to set both here? If both need to be set then you don't need the override.
Sau!
> BASE_PACKAGE_ARCH = "${BUILD_ARCH}"
> BASEPKG_HOST_SYS = "${BUILD_ARCH}${BUILD_VENDOR}-${BUILD_OS}"
> BASEPKG_TARGET_SYS = "${BUILD_ARCH}${BUILD_VENDOR}-${BUILD_OS}"
next prev parent reply other threads:[~2011-05-10 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 14:51 [PATCH 1/3] cmake.bbclass: fix qmake and rpath issues Otavio Salvador
2011-05-10 14:51 ` [PATCH 2/3] qmake_base.bbclass: add generate_qt_config_file task Otavio Salvador
2011-05-11 15:16 ` Richard Purdie
2011-05-10 14:51 ` [PATCH 3/3] cmake: add support for oe qt4 tools names Otavio Salvador
2011-05-11 15:17 ` Richard Purdie
2011-05-12 1:11 ` Otavio Salvador
2011-05-10 19:59 ` Saul Wold [this message]
2011-05-10 20:04 ` [PATCH 1/3] cmake.bbclass: fix qmake and rpath issues Otavio Salvador
2011-05-11 15:14 ` Richard Purdie
2011-05-11 15:15 ` Richard Purdie
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=4DC99913.1060403@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.