From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 3/4] infra: Introduce BR2_HOST_NEEDS_JAVA
Date: Tue, 18 Feb 2014 17:18:46 +0100 [thread overview]
Message-ID: <20140218171846.6969c9a6@skate> (raw)
In-Reply-To: <1392680233-24585-4-git-send-email-maxime.hadjinlian@gmail.com>
Dear Maxime Hadjinlian,
On Tue, 18 Feb 2014 00:37:12 +0100, Maxime Hadjinlian wrote:
> XBMC needs Java on the host in order to build, because it uses a
> code-generator which is build in two phases:
> In the first phase SWIG is used to parse C++ header files that define the API.
> SWIG outputs an XML file that contains a complete description of the structure
> of the API.
> In the second phase, the XML file is ingested by a Groovy (Java) program that
> then creates C++ code that forms the bridge to the scripting language (Python).
>
> The second phase is why we need java on the host.
People inventing such horrible code generation flows really have a
problem. They should probably talk to M-x doctor.
> +# Hidden boolean selected by packages in need of Java in order to build
> +# (example: xbmc)
> +config BR2_HOST_NEEDS_JAVA
> + bool
Do we need a kconfig bool for this? We have the same situation for
classpath, and we haven't introduced a specific kconfig bool for it.
Moreover, I am not sure BR2_HOST_NEEDS_JAVA is the right name. It's not
really the host that needs Java, it's the compilation process that
requires a host Java. So BR2_NEEDS_HOST_JAVA is probably more
technically correct.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-18 16:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 23:37 [Buildroot] [PATCH v7 0/4] Introducing XBMC Maxime Hadjinlian
2014-02-17 23:37 ` [Buildroot] [PATCH v7 1/4] sdl: add host version Maxime Hadjinlian
2014-02-18 16:13 ` Thomas Petazzoni
2014-02-18 16:41 ` Maxime Hadjinlian
2014-02-19 15:12 ` Peter Korsgaard
2014-02-17 23:37 ` [Buildroot] [PATCH v7 2/4] sdl_image: " Maxime Hadjinlian
2014-02-18 16:11 ` Thomas Petazzoni
2014-02-19 15:14 ` Peter Korsgaard
2014-02-19 15:14 ` Peter Korsgaard
2014-02-17 23:37 ` [Buildroot] [PATCH v7 3/4] infra: Introduce BR2_HOST_NEEDS_JAVA Maxime Hadjinlian
2014-02-18 16:18 ` Thomas Petazzoni [this message]
2014-02-18 16:41 ` Maxime Hadjinlian
2014-02-18 16:44 ` Thomas Petazzoni
2014-02-19 15:19 ` Peter Korsgaard
2014-02-17 23:37 ` [Buildroot] [PATCH v7 4/4] xbmc: new package Maxime Hadjinlian
2014-02-18 16:38 ` Thomas Petazzoni
2014-02-18 17:02 ` Maxime Hadjinlian
2014-02-18 18:30 ` Martin Bark
2014-02-19 0:14 ` Maxime Hadjinlian
2014-02-18 16:57 ` [Buildroot] [PATCH v7 0/4] Introducing XBMC Martin Bark
2014-02-18 17:03 ` Maxime Hadjinlian
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=20140218171846.6969c9a6@skate \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox