Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Stefan Hager <stefan.hager@ginzinger.com>,
	Samuel Martin <s.martin49@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 6/8] package/fft2d: new package
Date: Tue, 24 Jan 2023 11:37:13 +0200	[thread overview]
Message-ID: <87r0vkff25.fsf@tarshish> (raw)
In-Reply-To: <20230124092235.806969-6-james.hilliard1@gmail.com>

Hi James,

On Tue, Jan 24 2023, James Hilliard wrote:

> From: Stefan Hager <stefan.hager@ginzinger.com>
>
> This package is required by tensorflow-lite.
>
> This package doesn't provide a conventional install mechanism so
> we need to install it manually.
>
> Tested-by: Stefan Hager <stefan.hager@ginzinger.com>
> Signed-off-by: Stefan Hager <stefan.hager@ginzinger.com>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
>  DEVELOPERS               |  1 +
>  package/Config.in        |  1 +
>  package/fft2d/Config.in  |  7 +++++++
>  package/fft2d/fft2d.hash |  4 ++++
>  package/fft2d/fft2d.mk   | 22 ++++++++++++++++++++++
>  5 files changed, 35 insertions(+)
>  create mode 100644 package/fft2d/Config.in
>  create mode 100644 package/fft2d/fft2d.hash
>  create mode 100644 package/fft2d/fft2d.mk
>
> diff --git a/DEVELOPERS b/DEVELOPERS
> index a711f9f1ee..a2411bc749 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -2703,6 +2703,7 @@ F:	package/ti-gfx/
>  
>  N:	Stefan Hager <stefan.hager@ginzinger.com>
>  F:	package/cpuinfo/
> +F:	package/fft2d/
>  F:	package/gemmlowp/
>  F:	package/neon-2-sse/
>  F:	package/ruy/
> diff --git a/package/Config.in b/package/Config.in
> index 6377ddd2e5..dd16df061c 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -2003,6 +2003,7 @@ menu "Other"
>  	source "package/elfutils/Config.in"
>  	source "package/ell/Config.in"
>  	source "package/falcosecurity-libs/Config.in"
> +	source "package/fft2d/Config.in"
>  	source "package/fftw/Config.in"
>  	source "package/flann/Config.in"
>  	source "package/flatbuffers/Config.in"
> diff --git a/package/fft2d/Config.in b/package/fft2d/Config.in
> new file mode 100644
> index 0000000000..38394f6170
> --- /dev/null
> +++ b/package/fft2d/Config.in
> @@ -0,0 +1,7 @@
> +config BR2_PACKAGE_FFT2D
> +	bool "fft2d"
> +	help
> +	  This is a package to calculate Discrete Fourier/Cosine/Sine
> +	  Transforms of 2,3-dimensional sequences of length 2^N.
> +
> +	  http://www.kurims.kyoto-u.ac.jp/~ooura/fft.html
> diff --git a/package/fft2d/fft2d.hash b/package/fft2d/fft2d.hash
> new file mode 100644
> index 0000000000..a1b1a326ae
> --- /dev/null
> +++ b/package/fft2d/fft2d.hash
> @@ -0,0 +1,4 @@
> +# Locally calculated
> +sha256  ada7e99087c4ed477bfdf11413f2ba8db8a840ba9bbf8ac94f4f3972e2a7cec9  fft2d.tgz
> +# License files, locally calculated
> +sha256  0b2a2082537735a2a576dbec2e8f9c1a09812eac6df6a389502a6ba860072906  readme2d.txt
> diff --git a/package/fft2d/fft2d.mk b/package/fft2d/fft2d.mk
> new file mode 100644
> index 0000000000..6263b1af38
> --- /dev/null
> +++ b/package/fft2d/fft2d.mk
> @@ -0,0 +1,22 @@
> +################################################################################
> +#
> +# fft2d
> +#
> +################################################################################
> +
> +FFT2D_VERSION = 2006.12.28
> +FFT2D_SITE = https://www.kurims.kyoto-u.ac.jp/~ooura
> +FFT2D_SOURCE = fft2d.tgz
> +FFT2D_LICENSE = readme2d.txt

This does not look like a known license name.

baruch

> +FFT2D_LICENSE_FILES = readme2d.txt
> +FFT2D_INSTALL_STAGING = YES
> +FFT2D_INSTALL_TARGET = NO
> +
> +define FFT2D_INSTALL_STAGING_CMDS
> +	mkdir -p $(STAGING_DIR)/usr/include/fft2d
> +	$(INSTALL) -m 0644 $(@D)/*.c $(STAGING_DIR)/usr/include/fft2d
> +	$(INSTALL) -m 0644 $(@D)/*.f $(STAGING_DIR)/usr/include/fft2d
> +	$(INSTALL) -m 0644 $(@D)/*.h $(STAGING_DIR)/usr/include/fft2d
> +endef
> +
> +$(eval $(generic-package))


-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-01-24  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  9:22 [Buildroot] [PATCH v3 1/8] package/flatbuffers: build position independent code James Hilliard
2023-01-24  9:22 ` [Buildroot] [PATCH v3 2/8] package/cpuinfo: new package James Hilliard
2023-01-24  9:22 ` [Buildroot] [PATCH v3 3/8] package/ruy: " James Hilliard
2023-01-24  9:22 ` [Buildroot] [PATCH v3 4/8] package/gemmlowp: " James Hilliard
2023-01-24  9:22 ` [Buildroot] [PATCH v3 5/8] package/neon-2-sse: " James Hilliard
2023-01-24  9:22 ` [Buildroot] [PATCH v3 6/8] package/fft2d: " James Hilliard
2023-01-24  9:37   ` Baruch Siach via buildroot [this message]
2023-01-24  9:22 ` [Buildroot] [PATCH v3 7/8] package/farmhash: " James Hilliard
2023-01-24  9:22 ` [Buildroot] [PATCH v3 8/8] package/tensorflow-lite: " James Hilliard
2023-01-27  8:40   ` Lang Daniel via buildroot

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=87r0vkff25.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=fontaine.fabrice@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=s.martin49@gmail.com \
    --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