[PATCH 1/3] Compile oleaut32 for win32 but not for win64
truiken at gmail.com
Tue Oct 3 16:46:52 CDT 2006
On 10/3/06, Pavel Roskin <proski at gnu.org> wrote:
> Hello, James!
> On Tue, 2006-10-03 at 14:14 -0700, James Hawkins wrote:
> > On 10/3/06, Pavel Roskin <proski at gnu.org> wrote:
> > > From: Pavel Roskin <proski at gnu.org>
> > >
> > > Compile oleaut32 for win32 but not for win64
> > Does win64 not come with oleaut32? What I'm really asking is, why are
> > you making this change?
> It fails to compile. The error is "Invalid build platform for this
> Search for "oleaut32 wine win64" (without quotes) on Google to see
> multiple attempts to fix it somehow, for instance here:
> I understand oleaut32 can be fixed for win64, but nobody has done it.
> I believe my patch is worth applying because it enables Wine compilation
> without applying incorrect hacks to the sources. Instead, a mechanism
> is established to disable some parts of Wine for win64 until they are
> ported properly. We may need it for other files.
Removing oleaut32 from the build just hides the real problem, and
creates a slew of new problems. What will happen when an app tries to
use oleaut32 with a win64 build of Wine? The correct solution is to
fix oleaut32 to work with win64, no matter how difficult it is. We
can't allow temporary hacks in the meantime, or there will be
significantly less motivation to fix the real problem, because a
workaround is available.
More information about the wine-devel