[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Don't bother...
From:       Hin-Tak Leung <hintak_leung () yahoo ! co ! uk>
Date:       2008-03-30 17:35:26
Message-ID: 792997.74082.qm () web23105 ! mail ! ird ! yahoo ! com
[Download RAW message or body]

--- On Sat, 29/3/08, pure_evil@mail.bg <pure_evil@mail.bg> wrote:

> From: pure_evil@mail.bg <pure_evil@mail.bg>
> Subject: Don't bother...
> To: "Hin-Tak Leung" <hintak_leung@yahoo.co.uk>
> Date: Saturday, 29 March, 2008, 5:51 PM
> I tried compiling it against wine's source tree, it spat
> out a bunch of 
> warnings. When I wrote to him, that's what he replied:
> 
> > guess what, that's a different compiler.
> 'winegcc' != 'mingw32'. Did I say 
> something about crosscompiling? AFAIK you dont (cant?) use
> stuff compiled 
> with winegcc on windows because it depends on wine.
> 
> > I just thought you might want to look at a sample that
> builds and lives 
> outside so you could test you code on win too.
> 
> So, it's not what you think it is :( It's not
> usable as wine driver.

I am a bit lost about your comments. I have both winegcc and mingw32. 
I am quite familar with the latter and new to the former. 
I am using the appropriate ones (mingw32 for the printproxy, and winegcc for \
ddiwrapper). 

The printerproxy needs cross-compiling (and it works alright against current wine), \
ddiwrapper needs to be built with winegcc (and does not build against current wine).



      __________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox http://uk.docs.yahoo.com/nowyoucan.html


[prev in list] [next in list] [prev in thread] [next in thread]