Thank you very much, setting that flag helped!
Huỳnh Ngọc Thi
-so61pi
On Tue, May 30, 2017 at 8:34 PM, Petter Mabäcker wrote:
> Hi,
>
> If the problem is the footprint, then you can add below line in the
> libexample recipe:
>
> INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
>
> This will prevent the build
Hi,
If the problem is the footprint, then you can add below line
in the libexample recipe:
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
This
will prevent the build system from adding any debug info in the
libexample-dbg package.
BR Petter
[1] -
http://www.yoctoproject.org/docs/current/ref-manual/
I have both app-example*-dbg* & app-example in IMAGE_INSTALL and the result
is app-example-dbg & app-example & libexample-dbg & libexample are included
in the final image.
Huỳnh Ngọc Thi
-so61pi
On Mon, May 29, 2017 at 9:58 PM, Leonardo Sandoval <
leonardo.sandoval.gonza...@linux.intel.com> wrote
On Sun, 2017-05-28 at 17:23 +0700, Ngọc Thi Huỳnh wrote:
> Hi everyone,
>
>
> Let's say I have app-example package which depends on libexample.
>
> When I add app-example-dbg to IMAGE_INSTALL, libexample-dbg package is
> automatically included in the final image which makes the image size
> beco
Hi everyone,
Let's say I have app-example package which depends on libexample.
When I add app-example-dbg to IMAGE_INSTALL, libexample-dbg package is
automatically included in the final image which makes the image size become
bigger.
In this case, is there a way to prevent libexample-dbg from be
