On 12-06-20 11:25 AM, Paul Eggleton wrote:
On Wednesday 20 June 2012 10:31:40 Bruce Ashfield wrote:
From: Liang Li
...
+EXTRA_OEMAKE = \
+ '-C ${S}/tools/perf \
+ O=${B} \
+ CROSS_COMPILE=${TARGET_PREFIX} \
+ ARCH=${ARCH} \
+
On Wednesday 20 June 2012 10:31:40 Bruce Ashfield wrote:
> From: Liang Li
>...
> +EXTRA_OEMAKE = \
> + '-C ${S}/tools/perf \
> + O=${B} \
> + CROSS_COMPILE=${TARGET_PREFIX} \
> + ARCH=${ARCH} \
> + CC="${CC}" \
> + AR="${AR}"
On 12-06-20 11:00 AM, Saul Wold wrote:
On 06/20/2012 07:31 AM, Bruce Ashfield wrote:
From: Liang Li
perf has been coupled to the kernel packages via kernel.bbclass.
While maintaining the build of perf out of the kernel source tree
is desired the package coupling has proved to be awkward in
seve
On 06/20/2012 07:31 AM, Bruce Ashfield wrote:
From: Liang Li
perf has been coupled to the kernel packages via kernel.bbclass.
While maintaining the build of perf out of the kernel source tree
is desired the package coupling has proved to be awkward in
several situations such as:
- when a ker
From: Liang Li
perf has been coupled to the kernel packages via kernel.bbclass.
While maintaining the build of perf out of the kernel source tree
is desired the package coupling has proved to be awkward in
several situations such as:
- when a kernel recipe doesn't want to build/provide perf
