From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Including wine package - Reg
Date: Tue, 09 Apr 2013 23:58:34 +0200 [thread overview]
Message-ID: <51648F0A.502@mind.be> (raw)
In-Reply-To: <20130409232231.0b261d1a@skate>
On 09/04/13 23:22, Thomas Petazzoni wrote:
>> It throwed an error stating to use --with-wine-tools for cross compiling,
>> >hence I used
>> >WINE_CONF_OPT = --with-wine-tools=$(BUILD_DIR)/wine-$(WINE_VERSION)
> This looks odd. Why would the wine package require a reference to its
> own source directory? Doesn't sound correct.
>
wine-tools is a separate (host) package. Quick web search doesn't turn
up any archives, just git://source.winehq.org/git/tools.git
Arunkumar, I'm afraid integrating wine in buildroot will turn out to be
quite ambitious... I don't know what you are trying to do, but if it is
just a matter of building a very customized system and you don't really
care about cross-compilation, then you may be better off with e.g. Gentoo.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-04-09 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 19:49 [Buildroot] Including wine package - Reg Arunkumar Vijayakumar
2013-04-08 21:12 ` Thomas Petazzoni
2013-04-08 21:23 ` Arunkumar Vijayakumar
2013-04-08 21:31 ` Thomas Petazzoni
2013-04-08 21:44 ` Arunkumar Vijayakumar
2013-04-08 22:40 ` Arunkumar Vijayakumar
2013-04-09 18:16 ` Thomas Petazzoni
2013-04-09 21:19 ` Arunkumar Vijayakumar
2013-04-09 21:22 ` Thomas Petazzoni
2013-04-09 21:58 ` Arnout Vandecappelle [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=51648F0A.502@mind.be \
--to=arnout@mind.be \
--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.