From: Sascha Hauer <s.hauer@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: autotools for barebox host/target tools?
Date: Mon, 26 Feb 2018 08:40:11 +0100 [thread overview]
Message-ID: <20180226074011.lff7ytr6b6ylzbd7@pengutronix.de> (raw)
In-Reply-To: <20180222180026.GA32137@ravnborg.org>
On Thu, Feb 22, 2018 at 07:00:26PM +0100, Sam Ravnborg wrote:
> Hi Sasha.
>
> > I was just thinking, the kernel build system is great for compiling
> > barebox itself, but for compiling the userspace host and target tools
> > autotools would be a better match as they much better allow to specify
> > the necessary compilers and to pull the necessary dependencies in.
>
> What specific problems are you trying to solve that is
> not solved today by the support in scripts/Makefile.host?
No really specific problems. I just think that while handmade Makefiles
are good for the kernel/barebox, compiling userspace tools feels more
natural using widespread userspace build environments. Manually calling
pkg-config doesn't sound like a good idea and probably we would need
another pkg-config when compiling for the target. Now we normally do
not want to build the USB upload tools we have for the target, so this
argument doesn't really count.
>
> I notice you want to build tools for the target as well.
> This should be relatively easy to add support for that using
> the current kbuild syntax.
We do this already using targetprogs-y
>
> I we are going for something more standard then cmake or meson
> are more modern choices than the dreadful autotools stuff.
> And with modern I also imply better / simpler.
I didn't know about meson. This one sounds interesting and Michael
Olbrich, our build system expert, also has good things to tell about
meson.
As said, there are no concrete problems I wanted to solve, I just had
the vague feeling that for example integration into build systems
like YOCTO or ptxdist) might get simpler. Anyway, it was just an idea.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-02-26 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 8:03 Sascha Hauer
2018-02-22 14:20 ` Giorgio Dal Molin
2018-02-22 18:00 ` Sam Ravnborg
2018-02-26 7:40 ` Sascha Hauer [this message]
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=20180226074011.lff7ytr6b6ylzbd7@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sam@ravnborg.org \
/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