From: Ismael Luceno <ismael@iodev.co.uk>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC PATCH] docs/website: Add Makefile to pre-generate the website
Date: Tue, 6 Feb 2024 16:21:50 +0100 [thread overview]
Message-ID: <ZcJOjrDfe79fPfpz@pirotess> (raw)
In-Reply-To: <ZcJLd7drFQn9tz6I@landeda>
On 06/Feb/2024 16:08, Yann E. MORIN wrote:
<...>
> Make that gawk, so that we can do [0] (see below)
Mawk might be more complete than you think ;-).
> > +SRCDIR := ${CURDIR}
>
> Use parentheses not curly braces, to expand variables in Makefiles,
> like we do everyelse in Buildroot: $(..)
>
> (yes, both are valid, but lets be consistent throughout our code base)
OK, I'll change it for v3. I mentioned this before, according to
both GNU and BSD this is legacy syntax, and new stuff should use
curly braces...
<...>
> What is the rationale for using smu and tidy to do the deployement?
> We don't need/want to minimify the content...
smu is for having some markup support, not used for .html files; as
for tidy, it just normalises the html indentation, no minification is
going on.
<...>
> [0] In case of error, we do want to exit in error and be sure this is
> caught at the Makefile level; by using gawk, you can call:
>
> exit 42
That also works with any other AWK.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-06 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:40 [Buildroot] [RFC PATCH] docs/website: Add Makefile to pre-generate the website Ismael Luceno
2024-02-06 15:08 ` Yann E. MORIN
2024-02-06 15:21 ` Ismael Luceno [this message]
2024-02-06 16:30 ` Yann E. MORIN
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=ZcJOjrDfe79fPfpz@pirotess \
--to=ismael@iodev.co.uk \
--cc=buildroot@buildroot.org \
--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 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.