Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/xerces
Date: Wed, 21 Jan 2009 13:25:24 +0100	[thread overview]
Message-ID: <871vuwu9qj.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1232523074.11888.2.camel@elrond.atmel.com> (Ulf Samuelsson's message of "Wed\, 21 Jan 2009 08\:31\:14 +0100")

>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:

Hi,

 >> How about converting to Makefile.autotools.in format while you're at
 >> it?

 Ulf> I think my priority is to get things to build at all.

Then why were you doing cleanups as well in that commit?
Purely cosmetic cleanups to packages that should be converted to
Makefile.autotools.in seems kind of silly to me - But anyway.

 Ulf> Once all packages build, then it will not be hard
 Ulf> to get most of them into Makefile.autotools.in 

 Ulf> BTW: Makefile.autotools.in does not support compressed
 Ulf> patches *.patch.gz, *.patch.bz2, is that intentional?

Why should it?

find package/ -name '*patch.?z*'

We don't have such files, and for most patches in BR (with the
possible exception of those unfortunate avr32 patches) I don't think
compression will buy us much.

 ulf> xerces-clean:
 ulf> rm -rf $(STAGING_DIR)/usr/include/xercesc
 ulf> rm -f $(STAGING_DIR)/lib/libxerces*
 >> 
 >> TARGET_DIR cleanup stuff seems to be missing.

 Ulf> OK, Have a look at it later.

Thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-21 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 21:34 [Buildroot] svn commit: trunk/buildroot/package/xerces ulf at uclibc.org
2009-01-20 22:34 ` Peter Korsgaard
2009-01-21  7:31   ` Ulf Samuelsson
2009-01-21 12:25     ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-16 13:27 jacmet at uclibc.org

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=871vuwu9qj.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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