From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] lcms2: Install into staging
Date: Tue, 30 Dec 2014 20:39:32 +0100 [thread overview]
Message-ID: <54A2FF74.1040501@dawncrow.de> (raw)
In-Reply-To: <20141230051606.GD16594@tarshish>
Am 30.12.2014 um 06:16 schrieb Baruch Siach:
> Hi Andr?,
>
> On Tue, Dec 30, 2014 at 03:07:23AM +0100, Andr? Hentschel wrote:
>> Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
>> ---
>> package/lcms2/lcms2.mk | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/package/lcms2/lcms2.mk b/package/lcms2/lcms2.mk
>> index 5d22041..c2eda98 100644
>> --- a/package/lcms2/lcms2.mk
>> +++ b/package/lcms2/lcms2.mk
>> @@ -6,6 +6,7 @@
>>
>> LCMS2_VERSION = 2.5
>> LCMS2_SITE = http://downloads.sourceforge.net/lcms/lcms
>> +LCMS2_INSTALL_STAGING = YES
>
> Please explain in the commit log why you need this. The same goes for the next
> patch in this series (sane-backends).
>
> baruch
>
Hi Baruch,
I'm about to resend the patches and i hope to do it right.
But first i'd like to introduce myself quickly:
I'm a OSS developer from Germany, please find my openhub page here: https://www.openhub.net/accounts/Andre_H
Buildroot is great for testing software on different archictectures without finding a distro or something.
I'll try to get a Wine package upstream, i hope this work is welcome.
next prev parent reply other threads:[~2014-12-30 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 2:07 [Buildroot] [PATCH 1/2] lcms2: Install into staging André Hentschel
2014-12-30 2:07 ` [Buildroot] [PATCH 2/2] sane-backends: " André Hentschel
2014-12-30 5:16 ` [Buildroot] [PATCH 1/2] lcms2: " Baruch Siach
2014-12-30 19:39 ` André Hentschel [this message]
2014-12-30 19:40 ` [Buildroot] [PATCH 2/2 try 2] sane-backends: " André Hentschel
2015-01-01 15:51 ` Thomas Petazzoni
2015-01-01 17:38 ` André Hentschel
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=54A2FF74.1040501@dawncrow.de \
--to=nerv@dawncrow.de \
--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.