From: Herve Codina <herve.codina@bootlin.com>
To: buildroot@buildroot.org
Cc: "Hervé Codina" <herve.codina@bootlin.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH v3 0/5] Add Alchemy build system and some related libs
Date: Mon, 10 Jan 2022 15:50:02 +0100 [thread overview]
Message-ID: <20220110145007.133329-1-herve.codina@bootlin.com> (raw)
Hi,
This patch series introduces the Parrot Alchemy build system as a
host tool (patch 1).
This tool is then used to build several libs (patch 2, 3 and 4).
Finaly (patch 5), a test is provided to check that the binaries
were correctly built.
As it was mentionned by Thomas Peteazzoni in the previous review,
a new package infrastructure was not added for the Alchemy build system.
Indeed, we do not expect to have a significant number of packages that
will rely on the Alchemy build system.
Of course, should we have more of these packages in the future, we can
consider adding a package infrastructure.
This v3 series takes care of the Yann Morin's review.
Changes v2->v3 are detailed in each patch.
Best regards,
Hervé Codina
Herve Codina (5):
package/alchemy: new host package
package/ulog: new package
package/libfutils: new package
package/libshdata: new package
support/testing/tests/package/test_libshdata: new test
DEVELOPERS | 5 ++
package/Config.in | 3 +
...lchains-remove-hash-style-management.patch | 36 +++++++++
package/alchemy/alchemy.hash | 4 +
package/alchemy/alchemy.mk | 71 ++++++++++++++++++
package/alchemy/atom.mk.in | 8 ++
package/libfutils/Config.in | 15 ++++
package/libfutils/libfutils.hash | 3 +
package/libfutils/libfutils.mk | 56 ++++++++++++++
...01-backend-Add-missing-include-files.patch | 47 ++++++++++++
...stress_test-Fix-build-with-musl-libc.patch | 34 +++++++++
package/libshdata/Config.in | 29 +++++++
package/libshdata/libshdata.hash | 3 +
package/libshdata/libshdata.mk | 75 +++++++++++++++++++
package/ulog/Config.in | 12 +++
package/ulog/ulog.hash | 3 +
package/ulog/ulog.mk | 50 +++++++++++++
.../testing/tests/package/test_libshdata.py | 25 +++++++
18 files changed, 479 insertions(+)
create mode 100644 package/alchemy/0001-toolchains-remove-hash-style-management.patch
create mode 100644 package/alchemy/alchemy.hash
create mode 100644 package/alchemy/alchemy.mk
create mode 100644 package/alchemy/atom.mk.in
create mode 100644 package/libfutils/Config.in
create mode 100644 package/libfutils/libfutils.hash
create mode 100644 package/libfutils/libfutils.mk
create mode 100644 package/libshdata/0001-backend-Add-missing-include-files.patch
create mode 100644 package/libshdata/0002-examples-stress_test-Fix-build-with-musl-libc.patch
create mode 100644 package/libshdata/Config.in
create mode 100644 package/libshdata/libshdata.hash
create mode 100644 package/libshdata/libshdata.mk
create mode 100644 package/ulog/Config.in
create mode 100644 package/ulog/ulog.hash
create mode 100644 package/ulog/ulog.mk
create mode 100644 support/testing/tests/package/test_libshdata.py
--
2.33.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-01-10 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 14:50 Herve Codina [this message]
2022-01-10 14:50 ` [Buildroot] [PATCH v3 1/5] package/alchemy: new host package Herve Codina
2022-01-10 14:50 ` [Buildroot] [PATCH v3 2/5] package/ulog: new package Herve Codina
2022-01-10 14:50 ` [Buildroot] [PATCH v3 3/5] package/libfutils: " Herve Codina
2022-01-10 14:50 ` [Buildroot] [PATCH v3 4/5] package/libshdata: " Herve Codina
2022-01-10 14:50 ` [Buildroot] [PATCH v3 5/5] support/testing/tests/package/test_libshdata: new test Herve Codina
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=20220110145007.133329-1-herve.codina@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.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