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: Thu, 06 Sep 2012 16:57:09 +0100	[thread overview]
Message-ID: <5048C7D5.70301@communistcode.co.uk> (raw)
In-Reply-To: <5048BF04.2000904@communistcode.co.uk>

On 06/09/12 16:19, Jack Mitchell wrote:
> On 06/09/12 16:16, Phil Blundell wrote:
>> On Thu, 2012-09-06 at 16:15 +0100, Jack Mitchell wrote:
>>> On 06/09/12 16:09, Phil Blundell wrote:
>>>> On Thu, 2012-09-06 at 16:08 +0100, Jack Mitchell wrote:
>>>>> So, would the best way to fix it be something like:
>>>>>
>>>>> do_compile() {
>>>>>        run_oemake LD="${CCLD}"
>>>>> }
>>>> Yes, probably.  Or I guess you can just do:
>>>>
>>>> LD = "${CCLD}"
>>>>
>>>> somewhere else in your .bb file.
>> Oh, right.  It's a C++ program so what you actually need is LD="${CXX}".
>>
>> p.
>>
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> Perfect, I had CC=${CXX} so I was almost there!! : P
>
> Thanks for the help!
>

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?

Regards,


-- 

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

--




  reply	other threads:[~2012-09-06 16:08 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 [this message]
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
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=5048C7D5.70301@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