mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Giorgio Dal Molin <giorgio.nicole@arcor.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: autotools for barebox host/target tools?
Date: Thu, 22 Feb 2018 15:20:57 +0100 (CET)	[thread overview]
Message-ID: <1846760146.2938.1519309257312@mail.vodafone.de> (raw)
In-Reply-To: <20180222080357.7ces7vlsip6gnmxs@pengutronix.de>

Hi,

I have some experience with the gnu autotools.

Could you specify which tools you are thinking about ?

An alternative to the gnu autotools could also be 'meson'.

giorgio

> On February 22, 2018 at 9:03 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> 
> 
> Hi All,
> 
> 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.
> Any opinions or even volunteers?
> 
> 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

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-02-22 14:21 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 [this message]
2018-02-22 18:00 ` Sam Ravnborg
2018-02-26  7:40   ` Sascha Hauer

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=1846760146.2938.1519309257312@mail.vodafone.de \
    --to=giorgio.nicole@arcor.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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