From: Vadym Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bazel integration in buildroot
Date: Fri, 1 Mar 2019 14:19:38 +0200 [thread overview]
Message-ID: <20190301121938.GA21608@lwo1-lhp-f71841> (raw)
In-Reply-To: <CALFsTFU49uLC3aW+O62_oqa2v-tGeT8ZEqMpRjybSBcy4eGSWQ@mail.gmail.com>
Hi Asaf,
On Sun, Feb 24, 2019 at 06:24:40PM +0200, Asaf Kahlon wrote:
> Hello,
>
> At my work we started a process in which we want to choose a construction
> tool for our packages. Of course all the traditionals are on the list like
> cmake, meson and others, but we're also looking at Bazel from Google.
> All in all, Bazel seems like a nice construction tool, but I noticed that
> there's not even one package in Buildroot that compiles with Bazel and I
> wanted to know if we missed something. Is someone here familiar with this
> build system and can elaborate more details on Bazel in the embedded world
> and specifically in Buildroot?
>
> Regards,
> Asaf.
First of all I am not an expert, but I have some thoughts about this:)
It looks like bazel is a Java application ? if so, then there will one
more (I think big) dependency like Java on the host to build the bazel's
packages, or it may be built by openjdk buildroot's package (which is
not merged yet). Actually, bazel packages support might be added for local
usages only.
Anyway it is better if some of the buildroot experts can answer this question.
Regards,
Vadim Kochan
next prev parent reply other threads:[~2019-03-01 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 16:24 [Buildroot] Bazel integration in buildroot Asaf Kahlon
2019-03-01 12:19 ` Vadym Kochan [this message]
2019-03-01 15:33 ` Asaf Kahlon
2019-03-04 7:28 ` Arnout Vandecappelle
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=20190301121938.GA21608@lwo1-lhp-f71841 \
--to=vadim4j@gmail.com \
--cc=buildroot@busybox.net \
/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.