SDK

SDK

[Martin Townsend]

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

Hi,


I want to provide an SDK to the app developers that is a self contained
installation.  The ADT looked like just the thing except I don't want to
have to setup an ADT Repo.  I would like it to include:

The cross development toolchain.
The target sysroot to build against.  I would like them to be able to
dynamically link and statically link against everything in the Image.
They may want to develop kernel modules so I would want the kernel header
files etc in the target sysroot.
The Eclipse IDE Yocto plug-in or another way of using Eclipse to build and
debug for the target.
I Would also like to use things like the LTTNG and Valgrind integration in
Eclipse.
QEMU would be a nice to have and with integration into Eclipse.

I have my own distro and image files which aren't a million miles away from
poky and core-image-minimal :)

From what I've read I think the best thing for me to do is
bitbake my-image -cpopulate_sdk
which gives my an installer for the toolchain, target sysroot and qemu (I
think).
Then get them to install the Eclipse plugin by following the instructions
from
http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#adt-eclipse

Just want to check I'm on the right path and there's not another better way.

Many Thanks,
Martin.

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

Re: SDK

[Bryan Evenson]

Martin,

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Martin Townsend
> Sent: Saturday, November 14, 2015 9:27 AM
> To: yocto@yoctoproject.org
> Subject: [yocto] SDK
> 
> Hi,
> 
> 
> 
> I want to provide an SDK to the app developers that is a self contained
> installation.  The ADT looked like just the thing except I don't want to have to
> setup an ADT Repo.  I would like it to include:
> 
> 
> The cross development toolchain.
> 
> The target sysroot to build against.  I would like them to be able to
> dynamically link and statically link against everything in the Image.
> 
> They may want to develop kernel modules so I would want the kernel
> header files etc in the target sysroot.
> 
> The Eclipse IDE Yocto plug-in or another way of using Eclipse to build and
> debug for the target.
> I Would also like to use things like the LTTNG and Valgrind integration in
> Eclipse.
> 
> QEMU would be a nice to have and with integration into Eclipse.
> 
> 
> I have my own distro and image files which aren't a million miles away from
> poky and core-image-minimal :)
> 
> 
> From what I've read I think the best thing for me to do is
> 
> bitbake my-image -cpopulate_sdk
> 
> which gives my an installer for the toolchain, target sysroot and qemu (I
> think).

You need to make sure your image includes the features for debugging.  If you have an image that is based upon core-image-minimal, the image will be missing some features and you'll never be able to debug an application through Eclipse or use Lttng.

I'd suggest making a development image recipe (i.e. "my-custom-image-dev.bb") based on your image with the following changes:
1. Add "dev-pkgs eclipse-debug" to IMAGE_FEATURES
2. Add a "-dbg" package to IMAGE_INSTALL for each userspace application you are writing which you plan to debug with GDB.
3. Add "gdbserver" to IMAGE_INSTALL for GDB support.
4. Add "lttng-tools lttng-modules lttng-ust" to IMAGE_INSTALL for Lttng support.

Once you've built and verified the new image runs on your hardware, I'd then create the SDK as you described above.  I don't use QEMU so I can't speak to whether that gets included in the SDK or not.  But, if you have a developer that isn't responsible for building the whole image and just wants to build and debug their userspace application, the SDK and resulting sysroot should be all the pieces they need on their development machine.

Regards,
Bryan

> 
> Then get them to install the Eclipse plugin by following the instructions from
> http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#adt-
> eclipse
> 
> 
> Just want to check I'm on the right path and there's not another better way.
> 
> 
> Many Thanks,
> 
> Martin.
> 
> 

Re: SDK

[Martin Townsend]

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

Hi Bryan,

Thank you for the reply.  I'm just doing a dry run with some sample
applications using the SDK and the command line and all is looking good.  I
didn't know about the "eclipse-debug" so I'll take a look at this.  Sadly
all the dev and dbg packages are probably not going to fit into the flash
but I'll keep a copy of the dbg packages somewhere in case a developer
wants to debug into a library.  They can scp it onto their board and
install it.  If I also include gdbserver and lttng packages for the target
then hopefully this should be a good start.

Regards,
Martin.





On Mon, Nov 16, 2015 at 6:25 PM, Bryan Evenson <bevenson@melinkcorp.com>
wrote:

> Martin,
>
> > -----Original Message-----
> > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > bounces@yoctoproject.org] On Behalf Of Martin Townsend
> > Sent: Saturday, November 14, 2015 9:27 AM
> > To: yocto@yoctoproject.org
> > Subject: [yocto] SDK
> >
> > Hi,
> >
> >
> >
> > I want to provide an SDK to the app developers that is a self contained
> > installation.  The ADT looked like just the thing except I don't want to
> have to
> > setup an ADT Repo.  I would like it to include:
> >
> >
> > The cross development toolchain.
> >
> > The target sysroot to build against.  I would like them to be able to
> > dynamically link and statically link against everything in the Image.
> >
> > They may want to develop kernel modules so I would want the kernel
> > header files etc in the target sysroot.
> >
> > The Eclipse IDE Yocto plug-in or another way of using Eclipse to build
> and
> > debug for the target.
> > I Would also like to use things like the LTTNG and Valgrind integration
> in
> > Eclipse.
> >
> > QEMU would be a nice to have and with integration into Eclipse.
> >
> >
> > I have my own distro and image files which aren't a million miles away
> from
> > poky and core-image-minimal :)
> >
> >
> > From what I've read I think the best thing for me to do is
> >
> > bitbake my-image -cpopulate_sdk
> >
> > which gives my an installer for the toolchain, target sysroot and qemu (I
> > think).
>
> You need to make sure your image includes the features for debugging.  If
> you have an image that is based upon core-image-minimal, the image will be
> missing some features and you'll never be able to debug an application
> through Eclipse or use Lttng.
>
> I'd suggest making a development image recipe (i.e. "
> my-custom-image-dev.bb") based on your image with the following changes:
> 1. Add "dev-pkgs eclipse-debug" to IMAGE_FEATURES
> 2. Add a "-dbg" package to IMAGE_INSTALL for each userspace application
> you are writing which you plan to debug with GDB.
> 3. Add "gdbserver" to IMAGE_INSTALL for GDB support.
> 4. Add "lttng-tools lttng-modules lttng-ust" to IMAGE_INSTALL for Lttng
> support.
>
> Once you've built and verified the new image runs on your hardware, I'd
> then create the SDK as you described above.  I don't use QEMU so I can't
> speak to whether that gets included in the SDK or not.  But, if you have a
> developer that isn't responsible for building the whole image and just
> wants to build and debug their userspace application, the SDK and resulting
> sysroot should be all the pieces they need on their development machine.
>
> Regards,
> Bryan
>
> >
> > Then get them to install the Eclipse plugin by following the
> instructions from
> > http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#adt-
> > eclipse
> >
> >
> > Just want to check I'm on the right path and there's not another better
> way.
> >
> >
> > Many Thanks,
> >
> > Martin.
> >
> >
>
>

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

sdk

[C Michael Sundius]

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

Hi All,

I've been scratching my head all day about why I can build my recipe under
bitbake, but whne I try to build w/ the SDK I create w/ bitbake -c
populate_sdk <my-image> it cant find the headers for the libraries that I
depend upon.

somehow when I create the sdk, it does not include the header files for the
dependent libs. I see the .so files in the sysroot, but I don't see any of
the header files.

I don't see any of the headers for libxml2,  or the other libs.. those are
simply standard recipes from yocto.

any thoughts what am i doing wrong?

-----------------------
inherit abc-cmake
inherit pkgconfig
inherit systemd

EXTRA_OECMAKE_append = "\
    -DENABLE_SYSTEMD=ON \
    -DENABLE_API=ON \
    -DENABLE_CONFIG=ON \
    -DENABLE_UNITTEST=ON \
    -DENABLE_TUNCTL=ON \
    -DENABLE_WATCHDOG=ON \
    -DENABLE_AESNI=ON \
    -DFORCE_ALIGNMENT=OFF \
    -DENABLE_TRACE=OFF \
    -DENABLE_TUNING=OFF \
"

EXTRA_OECMAKE_append_abc-dev = " -DENABLE_TRACE=ON"
EXTRA_OECMAKE_append_abc-dbg = " -DENABLE_TUNING=ON"

LIC_FILES_CHKSUM = "file://COPYING;md5=8b5f7a1e89273c8fd243ca57ad73e483"

SRC_URI += "file://myprog.service"
SRC_URI += "file://myprog.conf"

SYSTEMD_SERVICE_${PN} = "myprog.service"
SYSTEMD_AUTO_ENABLE_${PN} = "enable"

do_install_append () {
        #install systemd service file
        install -d ${D}${systemd_system_unitdir}
        install -m 0644 ${WORKDIR}/udpf.service
${D}${systemd_system_unitdir}

        #install tmpfiles.d configuration file
        install -d ${D}${sysconfdir}/tmpfiles.d
        install -m 0644 ${WORKDIR}/udpf.conf ${D}${sysconfdir}/tmpfiles.d/
}


PACKAGES =+ "${PN}-utilities ${PN}-samples ${PN}-conf"

FILES_${PN} += "${sbindir}/dpfd"
FILES_${PN}-dev += "\
    ${sbindir}/segtest \
    ${sbindir}/ttest \
    ${sbindir}/workq \
"
FILES_${PN}-utilities += "${sbindir}/tunctl ${sbindir}/tapctl"
FILES_${PN}-samples += "${datadir}/*"
FILES_${PN}-conf += "${sysconfdir}/dpf/*"

RDEPENDS_${PN}-samples += "python"
DEPENDS = "libxml2 libevent nss systemd concurrencykit netmap"
RDEPENDS_${PN} = "libxml2 libevent nss systemd python-core
kernel-module-tun netmap"
RDEPENDS_${PN} += "libxml2 libevent nss-dev systemd python-core
kernel-module-tun netmap"

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

Re: sdk

[Joshua Watt]

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

On Mon, May 7, 2018, 17:26 C Michael Sundius <msundius@sundius.com> wrote:

> Hi All,
>
> I've been scratching my head all day about why I can build my recipe under
> bitbake, but whne I try to build w/ the SDK I create w/ bitbake -c
> populate_sdk <my-image> it cant find the headers for the libraries that I
> depend upon.
>
> somehow when I create the sdk, it does not include the header files for
> the dependent libs. I see the .so files in the sysroot, but I don't see any
> of the header files.
>
> I don't see any of the headers for libxml2,  or the other libs.. those are
> simply standard recipes from yocto.
>
> any thoughts what am i doing wrong?
>

Maybe  "dev-pkgs" was accidentally removed from SDKIMAGE_FEATURES?


> -----------------------
> inherit abc-cmake
> inherit pkgconfig
> inherit systemd
>
> EXTRA_OECMAKE_append = "\
>     -DENABLE_SYSTEMD=ON \
>     -DENABLE_API=ON \
>     -DENABLE_CONFIG=ON \
>     -DENABLE_UNITTEST=ON \
>     -DENABLE_TUNCTL=ON \
>     -DENABLE_WATCHDOG=ON \
>     -DENABLE_AESNI=ON \
>     -DFORCE_ALIGNMENT=OFF \
>     -DENABLE_TRACE=OFF \
>     -DENABLE_TUNING=OFF \
> "
>
> EXTRA_OECMAKE_append_abc-dev = " -DENABLE_TRACE=ON"
> EXTRA_OECMAKE_append_abc-dbg = " -DENABLE_TUNING=ON"
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=8b5f7a1e89273c8fd243ca57ad73e483"
>
> SRC_URI += "file://myprog.service"
> SRC_URI += "file://myprog.conf"
>
> SYSTEMD_SERVICE_${PN} = "myprog.service"
> SYSTEMD_AUTO_ENABLE_${PN} = "enable"
>
> do_install_append () {
>         #install systemd service file
>         install -d ${D}${systemd_system_unitdir}
>         install -m 0644 ${WORKDIR}/udpf.service
> ${D}${systemd_system_unitdir}
>
>         #install tmpfiles.d configuration file
>         install -d ${D}${sysconfdir}/tmpfiles.d
>         install -m 0644 ${WORKDIR}/udpf.conf ${D}${sysconfdir}/tmpfiles.d/
> }
>
>
> PACKAGES =+ "${PN}-utilities ${PN}-samples ${PN}-conf"
>
> FILES_${PN} += "${sbindir}/dpfd"
> FILES_${PN}-dev += "\
>     ${sbindir}/segtest \
>     ${sbindir}/ttest \
>     ${sbindir}/workq \
> "
> FILES_${PN}-utilities += "${sbindir}/tunctl ${sbindir}/tapctl"
> FILES_${PN}-samples += "${datadir}/*"
> FILES_${PN}-conf += "${sysconfdir}/dpf/*"
>
> RDEPENDS_${PN}-samples += "python"
> DEPENDS = "libxml2 libevent nss systemd concurrencykit netmap"
> RDEPENDS_${PN} = "libxml2 libevent nss systemd python-core
> kernel-module-tun netmap"
> RDEPENDS_${PN} += "libxml2 libevent nss-dev systemd python-core
> kernel-module-tun netmap"
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

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