From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6] wine: New package
Date: Thu, 19 Feb 2015 20:19:46 +0100 [thread overview]
Message-ID: <54E63752.90106@dawncrow.de> (raw)
In-Reply-To: <20150218220954.GA19555@free.fr>
Hi Yann, All,
Am 18.02.2015 um 23:09 schrieb Yann E. MORIN:
> Andre, All,
>
> On 2015-02-18 22:35 +0100, Andr? Hentschel spake thusly:
>> +WINE_DEPENDENCIES = host-bison host-flex host-wine
>> +
>> +# Wine needs to enable 64-bit build tools on 64-bit host
>> +ifeq ($(HOSTARCH),x86_64)
>> + HOST_WINE_CONF_OPTS += --enable-win64
>> +endif
>
> Please, keep all host-related stuff together. In this patch, you have
> some configure options here and at the end, and build+install commands
> here. Just move evrything host-related together (preferrably at the
> bottom of the file).
done for v7
>> +# Wine only needs the host tools to be built, so cut-down the
>> +# build time by building just what we need.
>> +HOST_WINE_BUILD_CMDS = \
>> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
>> + tools \
>> + tools/widl \
>> + tools/winebuild \
>> + tools/winegcc \
>> + tools/wmc \
>> + tools/wrc
>
> We use macros to define build commands:
>
> define HOST_WINE_BUILD_CMDS
> $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
> tools \
> tools/widl \
> tools/winebuild \
> tools/winegcc \
> tools/wmc \
> tools/wrc
> endef
done for v7
>
> Why TARGET_MAKE_ENV? You should use HOST_MAKE_ENV, since you're building
> a host package at that point.
fixed in v7, i copy&pasted to much from you ;)
> Otherwise, looks good. I'm queueing that for further inspection + tests
> this WE.
thx
prev parent reply other threads:[~2015-02-19 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 21:35 [Buildroot] [PATCH v6] wine: New package André Hentschel
2015-02-18 22:09 ` Yann E. MORIN
2015-02-19 19:19 ` André Hentschel [this message]
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=54E63752.90106@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox