Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] xerces: add host
Date: Fri, 22 Nov 2013 09:17:51 +0100	[thread overview]
Message-ID: <20131122091751.563a9ead@skate> (raw)
In-Reply-To: <OFDA43EF93.FECF1729-ON86257C2A.007C345A-86257C2A.007C6C20@rockwellcollins.com>

Dear Matthew Weber,

On Thu, 21 Nov 2013 16:39:01 -0600, Matthew Weber wrote:

> Opps, should have included that.
> 
> I'm working on adding support for an older package called xalan that 
> requires host-xerces.
> However the build infrastructure in the xalan package is pretty bad and 
> I'm not sure if I'll be 
> able to get it cleaned up to the point of posting a patch set.  So for 
> now, I've submitted 
> this patch to add host-xerces support to allow us to build the xalan 
> package using 
> BR2_EXTERNAL until I get it hopefully cleaned up and submitted.

Hum, okay. I'm generally not a big fan on having the host variant of
packages if they are not used by packages in Buildroot. I usually
prefer when the host variant of package A is added as part of a patch
set that allows adds package B, which depends on host-A. That being
said, I do understand the idea of upstreaming what you can for now, and
see later for the remaining things.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-11-22  8:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 19:48 [Buildroot] [PATCH 1/1] xerces: add host Matt Weber
2013-11-21 21:54 ` Thomas Petazzoni
2013-11-21 22:39   ` Matthew Weber
2013-11-22  8:17     ` Thomas Petazzoni [this message]
2013-11-22 16:54       ` Matthew Weber
2014-04-20 21:17 ` Thomas Petazzoni

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=20131122091751.563a9ead@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