All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Alexis Lothoré" <alexis.lothore@bootlin.com>,
	"Nicolas Carrier" <nicolas.carrier@nav-timing.safrangroup.com>
Subject: [Buildroot] [PATCH 0/2] package: bring two host tools
Date: Thu, 06 Aug 2026 23:24:21 +0200	[thread overview]
Message-ID: <20260806-host_tools-v1-0-19c63ecc3b10@bootlin.com> (raw)

Hello,
this small series aims to bring two new host packages to ease the
integration of web apps onto embedded platforms:
- uglifyjs ([1]), used to minify frontend assets,
- sass ([2]), a css extension adding programmation features to css.

Those two tools come in the shape of binaries installed in the host
directory. The use case supported by those new packages is the
possibility to run mini_asset ([3]) on host during some custom package
build, with uglifyjs and sass being two dependencies of it. The series
does not bring a mini_asset package though, as it can be brought by the
custom composer file in the final application project.

This use case kind of similar to what have been proposed in the past
with BR2_PACKAGE_HOST_NODEJS_MODULES_ADDITIONAL ([4]). At this time, the
proposal was rejected, and Arnout rather suggested to create dedicated
packages for this kind of host tools. This series follows this
suggestion, hoping that it is still the most relevant solution, 4 years
later. Another important point to mention is that the second package is
fetching some deps (npm install) at build step, which is not ideal, but
also suggested in Arnout's initial proposal. If that's not desired
anymore, I'm open to some guidance to improve this.

[1] https://www.npmjs.com/package/uglify-js
[2] https://www.npmjs.com/package/sass
[3] https://github.com/markstory/mini-asset
[4] https://lore.kernel.org/buildroot/20220119140703.12978-1-tom.marcuzzi@orolia.com/

---
Alexis Lothoré (2):
      package/uglifyjs: new package
      package/sass: new package

 DEVELOPERS                                         |  2 ++
 package/Config.in.host                             |  2 ++
 package/sass/Config.in.host                        |  8 ++++++
 package/sass/sass.hash                             |  3 +++
 package/sass/sass.mk                               | 30 ++++++++++++++++++++++
 package/uglifyjs/Config.in.host                    |  7 +++++
 package/uglifyjs/uglifyjs.hash                     |  3 +++
 package/uglifyjs/uglifyjs.mk                       | 23 +++++++++++++++++
 support/testing/tests/package/test_sass.py         | 23 +++++++++++++++++
 .../tests/package/test_sass/sample_sass.scss       |  7 +++++
 support/testing/tests/package/test_uglifyjs.py     | 23 +++++++++++++++++
 .../tests/package/test_uglifyjs/sample_uglifyjs.js |  5 ++++
 12 files changed, 136 insertions(+)
---
base-commit: 3c5c058d156daaba2901e539395a842d2bafd1e6
change-id: 20260806-host_tools-89a53a630ff7

Best regards,
--  
Alexis Lothoré <alexis.lothore@bootlin.com>

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2026-08-06 21:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 21:24 Alexis Lothoré via buildroot [this message]
2026-08-06 21:24 ` [Buildroot] [PATCH 1/2] package/uglifyjs: new package Alexis Lothoré via buildroot
2026-08-07  7:44   ` Thomas Petazzoni via buildroot
2026-08-10  8:44     ` Alexis Lothoré via buildroot
2026-08-06 21:24 ` [Buildroot] [PATCH 2/2] package/sass: " Alexis Lothoré via buildroot
2026-08-07  8:29   ` Thomas Petazzoni via buildroot
2026-08-07 11:55     ` Thomas Perale via buildroot
2026-08-10 12:25       ` Alexis Lothoré via buildroot
2026-08-10 21:04         ` Thomas Perale via buildroot
2026-08-10  9:29     ` Alexis Lothoré via buildroot
2026-08-10 12:32       ` Thomas Petazzoni 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=20260806-host_tools-v1-0-19c63ecc3b10@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=nicolas.carrier@nav-timing.safrangroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.