On Tue, 17 Jan 2017 20:54:14 Joshua Watt wrote:
> > external SDK:
> > everything the same as above, but for some packages there should be
> > only libraries - no header files.
>
> Is there a reason why you want the libraries without the headers? It
> doesn't seem particularly useful to be able to
Hi,
On 2017-01-18 04:54, Joshua Watt wrote:
external SDK:
everything the same as above, but for some packages there should be
only libraries - no header files.
Is there a reason why you want the libraries without the headers? It
doesn't seem particularly useful to be able to link a program
external SDK:
everything the same as above, but for some packages there should be
only libraries - no header files.
Is there a reason why you want the libraries without the headers? It
doesn't seem particularly useful to be able to link a program against a
library, but not have the header to
Hi,
A client would like to dish out an SDK to their customers, but only with
a subset of header files compared to those they use internally.
internal SDK:
As it is right now when you build an sdk with e.g. bitbake whatever -c
populate_sdk
external SDK:
everything the same as above, but for
