From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Wine package
Date: Fri, 02 Jan 2015 18:02:37 +0100 [thread overview]
Message-ID: <54A6CF2D.1090706@dawncrow.de> (raw)
Hi,
I'm working on the Wine package for upstream buildroot.
I attached Config.in and wine.mk for early review, so i don't start totally wrong.
Note that it's not complete wrt to dependency checking.
For cross compilation wine needs its own tools compiled for the host architecture, therefor there is host-wine.
As there's no easy way to only build the wine tools i disabled as much as possible.
Are stable or up-to-date (development) versions preferred? Wine 1.6.2 (latest stable) is one year old...
-------------- next part --------------
config BR2_PACKAGE_WINE
bool "Wine"
depends on BR2_INET_IPV6
depends on BR2_TOOLCHAIN_HAS_THREADS
# Wine has much CPU specific code
depends on BR2_i386 || BR2_x86_64
help
Wine is a compatibility layer capable of running
Windows applications on Linux. Instead of simulating internal
Windows logic like a virtual machine or emulator,
Wine translates Windows API calls into POSIX calls on-the-fly,
eliminating the performance and memory penalties of other methods.
http://www.winehq.org
comment "Wine needs a toolchain w/ IPv6, threads"
depends on BR2_i386 || BR2_x86_64
depends on !BR2_INET_IPV6 || !BR2_TOOLCHAIN_HAS_THREADS
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wine.mk
Type: text/x-makefile
Size: 4234 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150102/b11261be/attachment.bin>
next reply other threads:[~2015-01-02 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 17:02 André Hentschel [this message]
2015-01-02 18:13 ` [Buildroot] [RFC] Wine package Thomas Petazzoni
2015-01-02 18:56 ` André Hentschel
2015-01-02 19:29 ` Thomas Petazzoni
2015-01-03 16: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=54A6CF2D.1090706@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