($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "tom.hochstein@nxp.com" <tom.hochstein@nxp.com>
Cc: "meta-arm@lists.yoctoproject.org" <meta-arm@lists.yoctoproject.org>
Subject: Re: [meta-arm] [PATCH] arm/patrace: Add new package
Date: Wed, 10 Apr 2024 13:36:08 +0000	[thread overview]
Message-ID: <B3D7C5E1-36C9-432B-9AED-05E4E3AC90C6@arm.com> (raw)
In-Reply-To: <20240403163814.1978415-1-tom.hochstein@nxp.com>

On 3 Apr 2024, at 17:38, Tom Hochstein via lists.yoctoproject.org <tom.hochstein=nxp.com@lists.yoctoproject.org> wrote:
> +++ b/meta-arm/recipes-devtools/patrace/patrace_5.1.0.bb
> @@ -0,0 +1,36 @@
> +SUMMARY = "Software for capturing GLES calls of an application"
> +DESCRIPTION = "\
> +PATrace is software for capturing GLES calls of an application and \
> +replaying them on a different device, keeping the GPU workload the \
> +same. It's similar to the open source Apitrace project, but optimised \
> +for performance measurements."

Is this actually Arm-specific?  If it’s not then it feels like meta-oe is a better home for it.  If it is, then it needs a COMPATIBLE_MACHINE or similar to stop it building on platforms that are not supported.

> +    -DCMAKE_INSTALL_PREFIX:PATH=/opt/${BPN}”

Is there a good reason why this can’t be installed into $prefix?  If so, then a quick comment would be good.

Ross


      reply	other threads:[~2024-04-10 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 16:38 [PATCH] arm/patrace: Add new package Tom Hochstein
2024-04-10 13:36 ` Ross Burton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B3D7C5E1-36C9-432B-9AED-05E4E3AC90C6@arm.com \
    --to=ross.burton@arm.com \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=tom.hochstein@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).