From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: Samuel Martin <s.martin49@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 1/2] package/dlib: new package
Date: Sun, 15 Sep 2024 00:14:38 +0200 [thread overview]
Message-ID: <20240915001438.03ec32c4@windsurf> (raw)
In-Reply-To: <20240909121115.1165942-1-roykollensvendsen@gmail.com>
Hello Roy,
On Mon, 9 Sep 2024 14:11:12 +0200
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:
> Signed-off-by: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Thanks for the patch!
> Should I enforce using system libraries where alternative internal libraries exist?
Yes, we always want to use system libraries instead of bundled ones.
> Do I add too much license information here? (I assume I only need BSL-1.0)
I think the license information you provided is good as it is.
> diff --git a/package/dlib/Config.in b/package/dlib/Config.in
> new file mode 100644
> index 0000000000..77ff5086ae
> --- /dev/null
> +++ b/package/dlib/Config.in
> @@ -0,0 +1,60 @@
> +config BR2_PACKAGE_DLIB
> + bool "dlib"
> + depends on BR2_INSTALL_LIBSTDCPP
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + help
> + Dlib is a modern C++ toolkit containing machine learning
> + algorithms and tools for creating complex software in C++ to
> + solve real world problems.
> +
> + http://dlib.net
> +
> +if BR2_PACKAGE_DLIB
> +
> +config BR2_PACKAGE_DLIB_GIF_SUPPORT
> + bool "GIF support"
> + select BR2_PACKAGE_GIFLIB
I think you should drop all sub-options, and instead rely on automatic
dependencies, i.e:
ifeq ($(BR2_PACKAGE_GIFLIB),y)
... enable GIF support
else
... disable GIF support
endif
and ditto for all other options.
Last but not least, the addition of the entry in the DEVELOPERS file
should be done as part of the patch adding the package.
Could you adjust those small details and sent a new iteration, which I
believe we will be able to merge?
Thanks a lot!
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:[~2024-09-14 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 12:11 [Buildroot] [PATCH v4 1/2] package/dlib: new package Roy Kollen Svendsen
2024-09-09 12:11 ` [Buildroot] [PATCH v4 2/2] DEVELOPERS: add Roy Kollen Svendsen for dlib Roy Kollen Svendsen
2024-09-14 22:14 ` Thomas Petazzoni via buildroot [this message]
2024-09-15 4:58 ` [Buildroot] [PATCH v4 1/2] package/dlib: new package Roy Kollen Svendsen
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=20240915001438.03ec32c4@windsurf \
--to=buildroot@buildroot.org \
--cc=roykollensvendsen@gmail.com \
--cc=s.martin49@gmail.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