From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Stefan Hager <stefan.hager@ginzinger.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC PATCH 02/10] tensorflow-lite-clog: new package
Date: Thu, 24 Nov 2022 15:48:18 +0100 [thread overview]
Message-ID: <20221124154818.6ada922f@windsurf> (raw)
In-Reply-To: <20221124140627.3269192-3-stefan.hager@ginzinger.com>
Hello,
On Thu, 24 Nov 2022 15:06:19 +0100
Stefan Hager <stefan.hager@ginzinger.com> wrote:
> This package adds external sources required by tensorflow-lite.
> Nothing is built or installed within this package, but legal info and
> source archive is created. The tensorflow-lite makefile copies the
> files from this package and uses them for building or to provide
> headers for the staging folder.
Please wrap the commit logs to ~80 characters.
Isn't there a better way? It's really horrible to duplicate all those
packages that we already have in Buildroot :-/
> +TENSORFLOW_LITE_CLOG_SITE_METHOD = git
> +TENSORFLOW_LITE_CLOG_SITE = https://github.com/pytorch/cpuinfo
Are you sure? This looks like the URL for the cpuinfo package, not the
clog package.
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
next prev parent reply other threads:[~2022-11-24 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 14:06 [Buildroot] [RFC PATCH 00/10] tensorflow-lite: new package Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 01/10] tensorflow-lite-abseil-cpp: " Stefan Hager
2022-11-24 14:46 ` Thomas Petazzoni via buildroot
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 02/10] tensorflow-lite-clog: " Stefan Hager
2022-11-24 14:48 ` Thomas Petazzoni via buildroot [this message]
2022-11-25 16:21 ` James Hilliard
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 03/10] tensorflow-lite-abseil-cpuinfo: " Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 04/10] tensorflow-lite-eigen: " Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 05/10] tensorflow-lite-farmhash: " Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 06/10] tensorflow-lite-fft2d: " Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 07/10] tensorflow-lite-flatbuffers: " Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 08/10] tensorflow-lite-gemmlowp: " Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 09/10] tensorflow-lite-ruy: " Stefan Hager
2022-11-24 14:06 ` [Buildroot] [RFC PATCH 10/10] tensorflow-lite: " Stefan Hager
2022-11-24 14:54 ` [Buildroot] [RFC PATCH 00/10] " James Hilliard
[not found] ` <AM5PR06MB315361D4448EE9C17B1C3F65840E9@AM5PR06MB3153.eurprd06.prod.outlook.com>
2022-11-25 16:16 ` James Hilliard
2022-11-28 15:17 ` Hager Stefan
2022-11-28 18:02 ` James Hilliard
2022-11-30 6:43 ` Hager Stefan
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=20221124154818.6ada922f@windsurf \
--to=buildroot@buildroot.org \
--cc=stefan.hager@ginzinger.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox