All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Dudau <Adrian.Dudau@enea.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: dev-pkgs not installed in Extensible SDK
Date: Mon, 22 Jan 2018 14:33:02 +0000	[thread overview]
Message-ID: <1516631581.10186.2.camel@enea.com> (raw)

Adding dev-pkgs to SDKIMAGE_FEATURES I expected that the -dev packages
would be installed in the sysroot in the eSDK, but it seems that is
valid only for the standard SDK.

I have my own image that inherits core-image with various additions. In
the standard SDK, the debug folder under rpi_standard/sysroots/aarch64-
enea-linux/usr/src/debug shows like this:
acl          expat        less           libtirpc            make      
       rpcbind
atk          file         libaio         libtool             mingetty  
       rpm
attr         findutils    libarchive     libunistring        mpfr      
       rsync
babeltrace   fontconfig   libassuan      liburcu             ncurses   
       shadow
base-
passwd  freetype     libcap         libx11              nettle         
  shared-mime-info
bash         fuse         libcheck       libxau              nfs-
utils        slang
bc           gcc-
runtime  libcomps       libxcb              nspr             sqlite3
blktrace     gdbm         libdnf         libxcomposite       nss       
       strace
busybox      gdk-
pixbuf   libevent       libxcursor          openssh          systemd
bzip2        gettext      libffi         libxdamage          openssl   
       systemtap
cairo        glib-
2.0     libgcc         libxdmcp            pango            tcf-agent
ccache       glibc        libgpg-
error   libxext             patch            tcl
coreutils    gmp          libidn         libxfixes           pciutils  
       tcp-wrappers
curl         gnutls       libjpeg-
turbo  libxft              perl             trace-cmd
db           gpgme        libmpc         libxml2             pixman    
       util-linux
dbus         gtk+         libnfsidmap    libxml-parser-
perl  pkgconfig        xz
dhcp         harfbuzz     libnl          libxrandr           popt      
       zlib
diffstat     json-c       libpcre        libxrender          powertop
diffutils    kbd          libpng         lttng-tools         python3
e2fsprogs    kmod         librepo        lttng-ust           python3-
pygpgme
elfutils     latencytop   libsolv        m4                  readline


In the extensible SDK, I only have this under rpi/sysroots/aarch64-
enea-linux/usr/src/debug:
bash  bc  glibc  ncurses


I tried building both SDKs based on a vanilla core-image-minimal, and
the standard SDK has the sources installed as expected, but the ext SDK
has no debug folder containing sources. I tried

I tried looking into the populate_sdk* classes, but the code there is
very hard to understand at a first view. So I guess question is: Is
this intended by design or is it a bug? If intended, what is the
development worklfow for a user wanting to remote debug applications
using shared libraries?

Best regards,
--Adrian

             reply	other threads:[~2018-01-22 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 14:33 Adrian Dudau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-22 13:38 dev-pkgs not installed in Extensible SDK Adrian Dudau

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=1516631581.10186.2.camel@enea.com \
    --to=adrian.dudau@enea.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 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.