Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Issues building tinyXML
Date: Fri, 07 Sep 2012 09:16:22 +0100	[thread overview]
Message-ID: <5049AD56.8010808@communistcode.co.uk> (raw)
In-Reply-To: <5048D11C.9050108@communistcode.co.uk>

I think this has it cracked now.Phil, note the -fpic, is that in the 
right place?

DESCRIPTION = "A simple, small, C++ XML parser that can be easily 
integrated into other programs"

LICENSE = "zlib"
LIC_FILES_CHKSUM = 
"file://tinyxml.cpp;endline=23;md5=b97285d8fafcc49b761ca785816cc397"

SRC_URI = 
"http://ftp.debian.org/debian/pool/main/t/tinyxml/${PN}_${PV}.orig.tar.gz"

SRC_URI[md5sum] = "c1b864c96804a10526540c664ade67f0"
SRC_URI[sha256sum] = 
"15bdfdcec58a7da30adc87ac2b078e4417dbe5392f3afb719f9ba6d062645593"

S = "${WORKDIR}/tinyxml"

TINYXML_USE_STL = "YES"

do_compile() {
   oe_runmake LD="${CXX}"

   ${CXX} -fpic -shared -o lib${PN}.so.0.${PV} \
     -Wl,-soname,lib${PN}.so.0 $(ls *.o | grep -v xmltest)

}

do_install() {

   install -d -m 0755 ${D}${libdir}
   install -d -m 0755 ${D}${includedir}
   install -m 0755 lib${PN}.so.0.${PV} ${D}${libdir}
   install -m 0644 ${PN}.h tinystr.h ${D}${includedir}

   (cd ${D}${libdir}
     ln -s lib${PN}.so.0.${PV} lib${PN}.so.0
     ln -s lib${PN}.so.0.${PV} lib${PN}.so
   )

}


[jack@archHP packages-split]$ tree
.
|-- tinyxml
|   `-- usr
|       `-- lib
|           |-- libtinyxml.so.0 -> libtinyxml.so.0.2.6.2
|           `-- libtinyxml.so.0.2.6.2
|-- tinyxml-dbg
|   `-- usr
|       |-- lib
|       `-- src
|           `-- debug
|               `-- tinyxml-2.6.2-r0
|                   `-- tinyxml
|                       |-- tinystr.cpp
|                       |-- tinystr.h
|                       |-- tinyxml.cpp
|                       |-- tinyxmlerror.cpp
|                       |-- tinyxml.h
|                       `-- tinyxmlparser.cpp
|-- tinyxml-dev
|   `-- usr
|       |-- include
|       |   |-- tinystr.h
|       |   `-- tinyxml.h
|       `-- lib
|           `-- libtinyxml.so -> libtinyxml.so.0.2.6.2
|-- tinyxml-doc
|-- tinyxml-locale
|-- tinyxml.shlibdeps
`-- tinyxml-staticdev

17 directories, 12 files


-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  parent reply	other threads:[~2012-09-07  8:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 14:53 Issues building tinyXML Jack Mitchell
2012-09-06 14:59 ` Phil Blundell
2012-09-06 15:08   ` Jack Mitchell
2012-09-06 15:09     ` Phil Blundell
2012-09-06 15:15       ` Jack Mitchell
2012-09-06 15:16         ` Phil Blundell
2012-09-06 15:19           ` Jack Mitchell
2012-09-06 15:57             ` Jack Mitchell
2012-09-06 16:08               ` Phil Blundell
2012-09-06 16:15                 ` Jack Mitchell
2012-09-06 16:19                   ` Jack Mitchell
2012-09-06 16:19                   ` Phil Blundell
2012-09-06 16:36                     ` Jack Mitchell
2012-09-06 16:42                       ` Koen Kooi
2012-09-06 16:44                       ` Phil Blundell
2012-09-06 19:47                         ` Burton, Ross
2012-09-06 16:46                       ` Phil Blundell
2012-09-07  8:16                       ` Jack Mitchell [this message]
2012-09-13 18:01                         ` Andrei Gherzan

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=5049AD56.8010808@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --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