svn commit: r315245 - in head/emulators: . i386-wine-devel i386-wine-devel/files

[David Naylor]

On Tuesday, 26 March 2013 02:57:07 Sergey A. Osokin wrote:
> On Tue, Mar 26, 2013 at 08:13:03AM +0800, Martin Wilke wrote:
> > Why it calls i386-wine-devel? is wine-devel not just enough?
> 
> I'm not sure that its possible to run i386 windows binaries on
> amd64 with standard wine-devel port.

The wine situation appears to be rather complicated.  One can get:
 * wine for 32bit (emulators/wine and emulators/wine-devel) that runs on 
FreeBSD/i386, compiles on FreeBSD/i386
 * wine for 32bit (emulators/i386-wine-devel) that runs on FreeBSD/amd64, 
compiles on FreeBSD/i386
 * wine for 64bit (not ported) that runs on FreeBSD/amd64, will compile on 
FreeBSD/amd64
 * WoW64, wine for 32bit and 64bit (not ported) that runs on FreeBSD/amd64, 
this port (if and when ported) will supersede emulators/i386-wine-devel.  Will 
compile on FreeBSD/amd64 [1]

As for the particular naming, of i386, I followed the linux- convention where 
the prefix indicates a different architecture (but can still be installed).  

I have plans (very early plans) to allow i386 to be installed on FreeBSD/amd64 
by downloading the package (although no compilation on FreeBSD/amd64) and 
possibly integrating this port into the main port, but one step (port) at a 
time.  

[1] I think, wine might (probably) will require a compiler than can produce 
(cross-compile) 32bit binaries, which excludes base gcc.  

Regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20130326/dd7f0e8b/attachment.sig>