Posts by heitbaum

    Suggest you start with the below.


    which will error with the following. Only add dependancies to packages that you error on or you want the package compiled against. E.g. if you don’t want to use the h264 codec in a video app, then don’t include it … etc.


    As you are not developing a package that you need during the build process, all of your packages should be targets. And that is the default. So no need to use :host or :target for your development.


    If for example you needed to use the “mkimg” program to build a package “mkimg” because onnof the steps in building “mkimg” properly is to creat some images, and that uses the newly compiled “mkimg” program. You will need to compile both a host and target “mkimg”. Host to create you images, and target to run on your RPi.


    If you don’t need the mkimg program on your RPi, then you would only build mkimg:host.


    Hope that helps.


    Examples are cmake is a host only build.

    Hi nuive - probably not the best example to start with. glib is a package that builds for both the host that does the build and the target (your RPi3)


    In the case of your xxxx:host question - python:host is built “for the host” to be able to build glib.


    In your glib example - lib would be a dependency (on the RPi3 for your app)


    What application are you trying to package, might be able to give you some pointers on a package.mk to start with.

    Hi scaesare, correct on the squashfs, this is the SYSTEM in /flash. It (and the kernel) are updated on version updates. The /storage and /storage/.kodi/addon /storage/.config … are the user serviceable parts of LE. The validation / tracing to add this functionality will be to identify what chrome is doing, e.g. by trial and error or using strace or ….