Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Mauro Ziliani" <mauro@faresoftware.it>
To: Gabriele Zampieri <gabbla.malist@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [yocto] Adding libstdc++-dev path?
Date: Tue, 3 Dec 2019 12:23:41 +0100	[thread overview]
Message-ID: <ee49c8df-9035-d7ca-3f65-a911e7f938f0@faresoftware.it> (raw)
In-Reply-To: <CAAx3WaDTZBmR4bZw1asYtg8sAVzSX25EAqjDJ=RoaW7MX7jrvg@mail.gmail.com>

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

I try,

But libstdc++-dev is procudes by gcc-runtime recipe.

I try to put gcc-runtime in DEPENDS e RDEPENDS_${PN} but this doesn't.

Finally I put manually the -I${STAGING_INCDIR}/c++/5.3.0 
-I${STAGING_INCDIR}/c++/5.3.0/${CC_PREFIX} in the Makefile.

CC_PREFIX=arm-poky-linux-gnueabi

Il 03/12/19 11:55, Gabriele Zampieri ha scritto:
> Hi,
>
> have you tried adding libstdc++-dev to the recipe dependencies?
>
> DEPENDS += " libstdc++-dev"
>
> This will bring libstdc++ package into recipe sysroot and no extra 
> actions will be needed on compilation flags.
>
> Regards,
> Gabriele
>
> On Tue, Dec 3, 2019 at 11:44 AM Mauro Ziliani <mauro@faresoftware.it 
> <mailto:mauro@faresoftware.it>> wrote:
>
>     Hi all
>
>     I'm trying to compile a library which need cstdio.
>
>     The file is in ${STAGING_INCDIR}/c++/5.3.0 and in
>     ${STAGING_INCDIR}/c++/5.3.0/tr1
>
>     I think I need to "include" in my recipe all libstdc++dev package
>
>     Looking on ${CXX} -v I get
>     --with-gxx-include-dir=/not/exist/usr/include/c++/5.3.0
>
>
>     How can I use stdc by recipe?
>
>
>     Mauro
>
>     -=-=-=-=-=-=-=-=-=-=-=-
>     Links: You receive all messages sent to this group.
>
>     View/Reply Online (#47516):
>     https://lists.yoctoproject.org/g/yocto/message/47516
>     Mute This Topic: https://lists.yoctoproject.org/mt/65707284/3618237
>     Group Owner: yocto+owner@lists.yoctoproject.org
>     <mailto:yocto%2Bowner@lists.yoctoproject.org>
>     Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
>     [gabbla.malist@gmail.com <mailto:gabbla.malist@gmail.com>]
>     -=-=-=-=-=-=-=-=-=-=-=-
>

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

  reply	other threads:[~2019-12-03 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 10:44 Adding libstdc++-dev path? Mauro Ziliani
2019-12-03 10:55 ` [yocto] " Gabriele
2019-12-03 11:23   ` Mauro Ziliani [this message]
2019-12-03 12:59     ` Gabriele
2019-12-03 13:30       ` Mauro Ziliani

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=ee49c8df-9035-d7ca-3f65-a911e7f938f0@faresoftware.it \
    --to=mauro@faresoftware.it \
    --cc=gabbla.malist@gmail.com \
    --cc=yocto@yoctoproject.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