[pkg-wine-party] Bug#769234: Automatically detect wine32 and wine64.

[Jens Reyer]

On 12/13/2015 04:41 AM, Austin English wrote:
> On Sat, Dec 12, 2015 at 4:05 PM, Jens Reyer <jre.winesim at gmail.com> wrote:
>> 1.)
>> Checking with "file" (but honoring the WINE* variables first) allows to
>> continue to default to Wine32, while you still can install 64-bit apps
>> without manual intervention. However at least 64-bit apps with PE32
>> installers make this as a sole solution "problematic" and obfuscating
>> problems (-> consider tagging #769234 as "wontfix").
> 
> Wine will choose the appropriate loader without intervention. Choosing
> the architecture of the prefix should be up to the user.

Just to make sure I understood correctly: With a WoW64 (built with
--with-wine64=...") Wine:

If I *create* a new prefix then I decide about its arch (with the
default being win64) by using WINEARCH=...

But when I use an existing wineprefix, either with /usr/bin/wine
(vanilla upstream) or with a Desktop launcher, then Wine automatically
sets WINELOADER?


The latter indeed does not work with our current wine64. It could be
done with a system.reg test in our wine-script though.

I'm no programmer, but in server/registry.c I found:

----- snip -----
/* load a global option from the input file */
static int load_global_option( const char *buffer, struct file_load_info
*info )
{
    const char *p;

    if (!strncmp( buffer, "#arch=", 6 ))
    {
        enum prefix_type type;
        p = buffer + 6;
        if (!strcmp( p, "win32" )) type = PREFIX_32BIT;
        else if (!strcmp( p, "win64" )) type = PREFIX_64BIT;
----- snap -----

I have a feeling that Wine is doing the same like grep'ing system.reg
for #arch=win32 or #arch=win64. In that case I'd feel comfortable with
doing this in the wine script (unless^Wuntil we have a real WoW64
build). Better than having launchers that don't work and which don't
give the user any hint what's wrong.
Alternatively we could write the arch information in the launcher.


Mike, for a "back to back" WoW64 build you thought about cross-compiling
on amd64, or about copying results from one arch to the other/having the
amd64 packages as build-dependency for the WoW64 build on i386?


> I should clarify that. Upstream generally recommends packagers to ship
> WOW64 and enable that by default, yes. I was speaking with my
> bugzilla/user support hat on, where the first thing recommended if
> you're having issues is to use a 32-bit prefix (since a large portion
> of 64-bit installers don't work, and there's generally little gain for
> more problems, unless it's a memory intensive application).

ack

Greets
jre