How to include libstdc++ in an image?

How to include libstdc++ in an image?

[maniacbug]

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

Hi.  I am using denzil, trying to build a core-image-minimal with 
libstdc++ installed.  I want to cross-develop in c++, and run the 
resulting apps on the image.  For now, I am using qemu-arm as the 
machine.  I've been able to build and run core-image-minimal out of the 
box. build the cross tools, and build apps using the cross tools (and 
even add ssh to the image).  What I cannot figure out how to do is get 
libstdc++ (and libgcc1 and libc6) onto the target machine. 

The task-core-standalone-sdk-target looks super promising, 
seeming to contain the exact pieces I need.  I thought I could add this 
to the IMAGE_INSTALL line in core-image-minimal.bb, and have the libs 
show up.  This didn't happen, so clearly I have some more to learn about poky. 

Can anyone advise the appropriate way to inject libsdtc++ (and its dependencies) into a poky image?  Please note that I do not need to compile/link apps on the target, only run them.


Thanks!


[-- Attachment #2: Type: text/html, Size: 1203 bytes --]

Re: How to include libstdc++ in an image?

[Paul Eggleton]

On Tuesday 26 June 2012 19:22:20 maniacbug wrote:
> Hi.  I am using denzil, trying to build a core-image-minimal with
> libstdc++ installed.  I want to cross-develop in c++, and run the
> resulting apps on the image.  For now, I am using qemu-arm as the
> machine.  I've been able to build and run core-image-minimal out of the
> box. build the cross tools, and build apps using the cross tools (and
> even add ssh to the image).  What I cannot figure out how to do is get
> libstdc++ (and libgcc1 and libc6) onto the target machine.
> 
> The task-core-standalone-sdk-target looks super promising,
> seeming to contain the exact pieces I need.  I thought I could add this
> to the IMAGE_INSTALL line in core-image-minimal.bb, and have the libs
> show up.  This didn't happen, so clearly I have some more to learn about
> poky.
> 
> Can anyone advise the appropriate way to inject libsdtc++ (and its
> dependencies) into a poky image?  Please note that I do not need to
> compile/link apps on the target, only run them.

Adding libstdc++ to IMAGE_INSTALL should work - in fact I just tried it and it 
worked here (although I used the alternative of adding it to 
CORE_IMAGE_EXTRA_INSTALL in local.conf, but the result should be the same). 

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: How to include libstdc++ in an image?

[maniacbug]

>> Can anyone advise the appropriate way to inject libsdtc++ (and its
>> dependencies) into a poky image?  Please note that I do not need to
>> compile/link apps on the target, only run them.

> Adding libstdc++ to IMAGE_INSTALL should work - in fact I just tried it and it 
> worked here (although I used the alternative of adding it to 
> CORE_IMAGE_EXTRA_INSTALL in local.conf, but the result should be the same). 

Thanks!
 
Turns out this was user error.  libstdc++/libgcc were in fact included in the image, so it is correct that  task-core-standalone-sdk-target did the job.  I just had to remove the -dev packages to avoid balooning my image, so now I have a minimal image with ssh and libstdc++ < 10M.  Happiness.
 
Also handy to know that it works to just add package recipes directly to IMAGE_INSTALL.  Still learning bitbake, so it's not clear what goes there versus IMAGE_FEATURES, etc.

Re: How to include libstdc++ in an image?

[Koen Kooi]

Op 28 jun. 2012, om 12:56 heeft Paul Eggleton het volgende geschreven:

> On Tuesday 26 June 2012 19:22:20 maniacbug wrote:
>> Hi.  I am using denzil, trying to build a core-image-minimal with
>> libstdc++ installed.  I want to cross-develop in c++, and run the
>> resulting apps on the image.  For now, I am using qemu-arm as the
>> machine.  I've been able to build and run core-image-minimal out of the
>> box. build the cross tools, and build apps using the cross tools (and
>> even add ssh to the image).  What I cannot figure out how to do is get
>> libstdc++ (and libgcc1 and libc6) onto the target machine.
>> 
>> The task-core-standalone-sdk-target looks super promising,
>> seeming to contain the exact pieces I need.  I thought I could add this
>> to the IMAGE_INSTALL line in core-image-minimal.bb, and have the libs
>> show up.  This didn't happen, so clearly I have some more to learn about
>> poky.
>> 
>> Can anyone advise the appropriate way to inject libsdtc++ (and its
>> dependencies) into a poky image?  Please note that I do not need to
>> compile/link apps on the target, only run them.
> 
> Adding libstdc++ to IMAGE_INSTALL should work - in fact I just tried it and it 
> worked here (although I used the alternative of adding it to 
> CORE_IMAGE_EXTRA_INSTALL in local.conf, but the result should be the same). 

But do note that if you ship libstdc++ without anything linking to it you forego on the linking exception to the GPL. That is general is a Very Bad Thing(TM), so ship a helloword.cpp binary to keep the fsf happy. As an added bonus the helloworld will drag in the lib automatically.

Re: How to include libstdc++ in an image?

[Paul Eggleton]

On Saturday 30 June 2012 23:56:18 Koen Kooi wrote:
> But do note that if you ship libstdc++ without anything linking to it you
> forego on the linking exception to the GPL. That is general is a Very Bad
> Thing(TM), so ship a helloword.cpp binary to keep the fsf happy. As an
> added bonus the helloworld will drag in the lib automatically.

[citation needed]

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: How to include libstdc++ in an image?

[Khem Raj]

On Sat, Jun 30, 2012 at 3:29 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
>
> [citation needed]

this is an interpretation of GPL-3, I dont have citations to hand here though.

Re: How to include libstdc++ in an image?

[William Mills]

On 06/30/2012 06:29 PM, Paul Eggleton wrote:
> On Saturday 30 June 2012 23:56:18 Koen Kooi wrote:
>> But do note that if you ship libstdc++ without anything linking to it you
>> forego on the linking exception to the GPL. That is general is a Very Bad
>> Thing(TM), so ship a helloword.cpp binary to keep the fsf happy. As an
>> added bonus the helloworld will drag in the lib automatically.
>
> [citation needed]
>

I agree with Koen.

I have had discussion with the FSF and others in the open source 
compliance arena.  The first sentence appears to be the prevailing 
interpretation.  I have asked the FSF to clarify its position on the FAQ 
but no luck so far.

Bill

Re: How to include libstdc++ in an image?

[maniacbug]

> But do note that if you ship libstdc++ without anything linking to it you forego on the linking
> exception to the GPL. That is general is a Very Bad Thing(TM), so ship a helloword.cpp 
> binary to keep the fsf happy. As an added bonus the helloworld will drag in the lib automatically.

Thanks for the advice.  I had no idea.  Although personally I am SO far from shipping right now :)
Still good to be aware of this.