Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Romain Naour <romain.naour@smile.fr>
Cc: David Picard <david.picard@clermont.in2p3.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/intel-socfpga-hwlib: add new package
Date: Wed, 21 Feb 2024 07:28:20 +0100	[thread overview]
Message-ID: <ZdWYBJ7mt1L2CTjL@landeda> (raw)
In-Reply-To: <643b99fe-655d-45b9-80dd-f47bb53efcb2@smile.fr>

Romain, David, All,

On 2024-02-20 23:26 +0100, Romain Naour spake thusly:
> Le 20/02/2024 à 22:18, David Picard a écrit :
[--SNIP--]
> >>> +INTEL_SOCFPGA_HWLIB_LICENSE = PROPRIETARY
> >> It's unexpected to find a PROPRIETARY tool in a gitbub accound with "opensource"
> >> in their name :)

It's not common, but we do already have a bunch of such packages:

    $ git grep -E 'PROPRIETARY\>' package/ boot/ |wc -l
    13

[--SNIP--]
> > I did it on purpose. This package is called a library, but it really is a bunch
> > of C files. You only use a subset, depending on your hardware. This code was
> > made to be compiled in the application, not as a conventional library.
> > I could copy the files to STAGING, but cleaning would be more complicated and it
> > would waste some disk space.
> Ok, maybe is should not be packaged in Buildroot then.
> When a package is build by Buildroot, it can generate a binary, a library or
> provide some header files.
> If your application doesn't bundle intel-socfpga-hwlib sources but it requires
> it to build in Buildroot, you can use LIBFOO_EXTRA_DOWNLOADS to add an extra
> download step.

I agree with Romain. It does not make miuch sense IMHO to just drop
source files like that. And the _EXTRA_DOWNLOADS mechanism is exactly
tailored to such cases.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-21  6:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  9:34 [Buildroot] [PATCH 1/1] package/intel-socfpga-hwlib: add new package David Picard
2024-02-14 16:23 ` Romain Naour
2024-02-15  7:40   ` David Picard
2024-02-20 21:18   ` David Picard
2024-02-20 22:26     ` Romain Naour
2024-02-21  6:28       ` Yann E. MORIN [this message]
2024-02-21  8:36         ` David Picard
2024-02-21 12:25           ` David Picard
2024-02-21 15:33             ` Romain Naour
2024-02-22 10:09               ` David Picard
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14  9:32 David Picard
2024-02-14  9:29 David Picard
2024-02-14  8:19 David Picard
2024-02-13 16:31 David Picard

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=ZdWYBJ7mt1L2CTjL@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=david.picard@clermont.in2p3.fr \
    --cc=romain.naour@smile.fr \
    /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