From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/4] python-cheetah: add host-package support
Date: Thu, 5 Mar 2015 09:54:10 +0100 [thread overview]
Message-ID: <20150305095410.612bea91@free-electrons.com> (raw)
In-Reply-To: <20150305094049.055a39b7@x230.trabucayre.com>
Hello,
On Thu, 5 Mar 2015 09:40:49 +0100, gwenhael.goavec wrote:
> I'm wrong, it's true, host-python-markdown is only needed for
> host-python-cheetah. I think the best solution is the second option, ie.
> PYTHON_CHEETAH_DEPENDENCIES = python-markdown to be sure to have the correct
> dependency in all case (although python-cheetah as not really needed to
> python-markdown to be compiles).
If only host-python-markdown is needed to build host-python-cheetah,
then the correct solution is:
HOST_PYTHON_CHEETAH_DEPENDENCIES = host-python-markdown
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-05 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 16:00 [Buildroot] [PATCH v3 1/4] pkg-cmake: allow to build package in a subdirectory Gwenhael Goavec-Merou
2015-03-04 16:00 ` [Buildroot] [PATCH v3 2/4] python-markdown: add host-package support Gwenhael Goavec-Merou
2015-03-04 21:47 ` Thomas Petazzoni
2015-03-04 16:00 ` [Buildroot] [PATCH v3 3/4] python-cheetah: " Gwenhael Goavec-Merou
2015-03-04 21:49 ` Thomas Petazzoni
2015-03-05 8:40 ` gwenhael.goavec
2015-03-05 8:54 ` Thomas Petazzoni [this message]
2015-03-04 16:00 ` [Buildroot] [PATCH v3 4/4] GNURadio: new package Gwenhael Goavec-Merou
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=20150305095410.612bea91@free-electrons.com \
--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