Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] libtinyxml: Add native support and use relative paths
Date: Fri, 22 Mar 2013 10:22:18 +0100	[thread overview]
Message-ID: <20130322092218.GL3219@jama> (raw)
In-Reply-To: <1363279557-5861-1-git-send-email-stefan@herbrechtsmeier.net>

[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]

On Thu, Mar 14, 2013 at 05:45:57PM +0100, Stefan Herbrechtsmeier wrote:
> Replace CXXFLAGS += "-fPIC" with EXTRA_CXXFLAGS to allow native
> build and use relative paths to simplify recipe.

Applied, thanks!

> 
> Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
> ---
>  .../recipes-support/libtinyxml/libtinyxml_2.6.2.bb |   18 ++++++++++--------
>  1 files changed, 10 insertions(+), 8 deletions(-)
> 
> diff --git a/meta-oe/recipes-support/libtinyxml/libtinyxml_2.6.2.bb b/meta-oe/recipes-support/libtinyxml/libtinyxml_2.6.2.bb
> index fdadebd..8670fac 100644
> --- a/meta-oe/recipes-support/libtinyxml/libtinyxml_2.6.2.bb
> +++ b/meta-oe/recipes-support/libtinyxml/libtinyxml_2.6.2.bb
> @@ -16,20 +16,21 @@ SRC_URI[sha256sum] = "15bdfdcec58a7da30adc87ac2b078e4417dbe5392f3afb719f9ba6d062
>  
>  S = "${WORKDIR}/tinyxml"
>  
> -CXXFLAGS += "-fPIC"
> +EXTRA_CXXFLAGS = "-I. -fPIC"
>  
>  do_compile() {
> -    ${CXX} ${CXXFLAGS} -I${S} -c -o ${S}/tinyxml.o ${S}/tinyxml.cpp
> -    ${CXX} ${CXXFLAGS} -I${S} -c -o ${S}/tinyxmlerror.o ${S}/tinyxmlerror.cpp
> -    ${CXX} ${CXXFLAGS} -I${S} -c -o ${S}/tinyxmlparser.o ${S}/tinyxmlparser.cpp
> +    ${CXX} ${CXXFLAGS} ${EXTRA_CXXFLAGS} -c -o tinyxml.o tinyxml.cpp
> +    ${CXX} ${CXXFLAGS} ${EXTRA_CXXFLAGS} -c -o tinyxmlerror.o tinyxmlerror.cpp
> +    ${CXX} ${CXXFLAGS} ${EXTRA_CXXFLAGS} -c -o tinyxmlparser.o tinyxmlparser.cpp
>      ${CXX} ${CXXFLAGS} \
>              -shared \
>              -Wl,-soname,libtinyxml.so.${PV} \
> -            -o ${S}/libtinyxml.so.${PV} \
> +            -o libtinyxml.so.${PV} \
>              ${LDFLAGS} \
> -            ${S}/tinyxml.o \
> -            ${S}/tinyxmlparser.o \
> -            ${S}/tinyxmlerror.o
> +            tinyxml.o \
> +            tinyxmlparser.o \
> +            tinyxmlerror.o
> +
>  }
>  
>  do_install() {
> @@ -41,3 +42,4 @@ do_install() {
>      install -m 0644 ${S}/tinyxml.h ${D}${includedir}
>  }
>  
> +BBCLASSEXTEND += "native"
> -- 
> 1.7.0.4
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-03-22  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 16:45 [meta-oe][PATCH] libtinyxml: Add native support and use relative paths Stefan Herbrechtsmeier
2013-03-22  9:22 ` Martin Jansa [this message]

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=20130322092218.GL3219@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox