From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Issues building tinyXML
Date: Thu, 06 Sep 2012 17:15:46 +0100 [thread overview]
Message-ID: <5048CC32.30705@communistcode.co.uk> (raw)
In-Reply-To: <1346947708.2673.201.camel@phil-desktop>
On 06/09/12 17:08, Phil Blundell wrote:
> On Thu, 2012-09-06 at 16:57 +0100, Jack Mitchell wrote:
>> I take this back, It built correctly but it seems the makefile doesn't
>> build the shared library to link against?!
>>
>> The Archlinux package has something similar to:
>>
>> ${CXX} -shared -o lib${PN}.so.0.${PV} \
>> -Wl,-soname,lib${PN}.so.0 $(ls *.o | grep -v xmltest)
>>
>> Which seems to collect all the objects and link them together into a
>> shared object? Is there anywhere else in OE we do this so I could see
>> how it is formally done?
> Yeah, pretty much that. If you're going to make it into a DSO then you
> also need to make sure that all the objects are compiled -fpic.
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Ok, so this is where I am at:
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)
}
FILES_${PN} = "libtinyxml.so.0.${PV}}"
However, libtinyxml.so.0.${PV} doesn't get packaged, even though it is
listed in the {S} directory. Am I missing something with the FILES_${PN}?
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-09-06 16: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 [this message]
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
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=5048CC32.30705@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 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.