Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Angelo Compagnucci <angelo@amarulasolutions.com>
Cc: Matt Flax <flatmax@flatmax.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v6] package/gtkiostream: new package
Date: Sun, 14 Jul 2024 19:02:01 +0200	[thread overview]
Message-ID: <20240714190201.589e7b3e@windsurf> (raw)
In-Reply-To: <20230208100704.68093-1-angelo@amarulasolutions.com>

Hello Matt, Hello Angelo,

On Wed,  8 Feb 2023 11:07:04 +0100
Angelo Compagnucci <angelo@amarulasolutions.com> wrote:

> From: Matt Flax <flatmax@flatmax.com>
> 
> This package provides many useful software engineering and signal
> processing libraries.
> 
> Signed-off-by: Matt Flax <flatmax@flatmax.com>
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
> ---
> v4:                             
> * Bumped to 1.8.0                                                
> * Added myself to DEVELOPERS                                     
> * Added dependency on octave when enable instead of use
>   --disable-octave configure option                                                                                               
> * Fixes from check-package                                                                                                        
> v5:                                                              
> * Fixed wrong syntax (Romain)                                    
> * Added optional dependency on sox (Matt) 
> v6:
> * Fixing fomatting (Thmos P.)
> * Adding optional flag for openmp
> * Adding patch to disable testing compilation:
>   build wasfailing for some incompatible linking option in one of the
>   tests. Tests are not useful for the buildroot usecase therefore they
>   are disabled.

I have finally merged this patch (yeah, sorry for the big delay!), with
quite a lot of changes:

- Made the patch upstreamable by adding a ./configure option, and
  actually submitted the patch upstream. Added the Upstream: tag
  pointing to the pull request

- Adding "threads" to the Config.in comment about dependencies

- Handling all optional dependencies, since they don't have any
  --disable-<foo> option.

See https://gitlab.com/buildroot.org/buildroot/-/commit/fab48302865e5c0c98d91b696bc90e75e38189bb
for the final commit.

I've seen upstream has a lot of commits on top of 1.8.0. It would be
nice for upstream (hint, hint!) to do a new release that includes all
those improvements, so that we can update the package in Buildroot.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-07-14 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 10:07 [Buildroot] [PATCH v6] package/gtkiostream: new package Angelo Compagnucci
2023-02-08 10:53 ` Thomas Petazzoni via buildroot
2024-07-14 17:02 ` 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=20240714190201.589e7b3e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=angelo@amarulasolutions.com \
    --cc=flatmax@flatmax.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