From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Rufus Segar <rhs@riseup.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package: add agent-proxy target and host packages
Date: Fri, 14 Oct 2022 23:11:47 +0200 [thread overview]
Message-ID: <20221014231147.05459ac1@windsurf> (raw)
In-Reply-To: <20220507161338.2125859-1-rhs@riseup.net>
Hello Rugus,
On Sat, 7 May 2022 17:13:37 +0100
Rufus Segar <rhs@riseup.net> wrote:
> Signed-off-by: Rufus Segar <rhs@riseup.net>
Thanks a lot for your contribution. Believe it or not, but after some
many months, I finally took the time to review and apply your patch.
However, I did quite a few changes:
- I kept only the host variant of the package. Indeed, my
understanding is that agent-proxy is meant to be executed on the
developer workstation to de-multiplex the kgdb traffic from the
console traffic. Therefore it was not clear why a target variant was
needed. Of course, if additional justification/explanation is given,
the target variant can be re-added via a follow-up patch.
- Addition of an entry in the DEVELOPERS file
- Addition of a .hash file with the hash of the tarball and hash of
the COPYING file.
See below for some other comments.
> +AGENT_PROXY_VERSION = agent-proxy-1.97
> +AGENT_PROXY_SITE = git://git.kernel.org/pub/scm/utils/kernel/kgdb/agent-proxy.git
> +AGENT_PROXY_LICENSE = GPL-2.0+
This was not correct: the license is GPL-2.0 only.
> +AGENT_PROXY_LICENSE_FILES = COPYING
> +
> +define AGENT_PROXY_BUILD_CMDS
> + $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) all
> +endef
> +
> +define AGENT_PROXY_INSTALL_STAGING_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/agent-proxy $(STAGING_DIR)/usr/bin
This had not effect since AGENT_PROXY_INSTALL_STAGING is not set to
YES. But anyway, I dropped this since I dropped the target variant;
> +endef
> +
> +define AGENT_PROXY_INSTALL_TARGET_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/agent-proxy $(TARGET_DIR)/usr/bin
> +endef
> +
> +define HOST_AGENT_PROXY_BUILD_CMDS
> + $(HOST_CONFIGURE_OPTS) $(MAKE) -C $(@D)
> +endef
> +
> +define HOST_AGENT_PROXY_INSTALL_CMDS
> + $(HOST_CONFIGURE_OPTS) $(INSTALL) -D -m 0755 $(@D)/agent-proxy $(HOST_DIR)/bin
$(HOST_CONFIGURE_OPTS) not needed here, and we want the full
destination path as the last argument, i.e $(HOST_DIR)/bin/agent-proxy.
Once again, thanks a lot for this contribution!
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-10-14 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 16:13 [Buildroot] [PATCH 1/1] package: add agent-proxy target and host packages Rufus Segar
2022-05-07 16:13 ` [Buildroot] [PATCH 1/1] package: add kdmx " Rufus Segar
2022-10-14 21:14 ` Thomas Petazzoni via buildroot
2022-10-14 21:11 ` Thomas Petazzoni via buildroot [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=20221014231147.05459ac1@windsurf \
--to=buildroot@buildroot.org \
--cc=rhs@riseup.net \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.