On Sun, Jun 27, 2010 at 4:59 AM, Aleksey Bragin wrote:
> Is there any real, practical interest in Wine on Windows?
For doing a full port, other than the argument of climbing the
mountain because it's there, I doubt it.
> I've been making some progress in this direction recently (though I think m
For dx10 you just need wined3d and the client libs. Those work since quite a
while without any other wine component
ng able to run 16-bit
> Windows apps on 64-bit Windows! :P
16-bit compilation is currently disabled in Cygwin. There's a list of
ideas on http://wiki.winehq.org/WineOnWindows -
* As much as possible should compile (and even work).
* Check how well the .EXE and .DLL made by Wine on Cygwin wo
On Sun, Jun 27, 2010 at 3:59 AM, Aleksey Bragin wrote:
> Is there any real, practical interest in Wine on Windows?
> I've been making some progress in this direction recently (though I think
> my approach would be to have a ported, NT-version of wineserver.exe which
> just uses native functions o
Is there any real, practical interest in Wine on Windows?
I've been making some progress in this direction recently (though I
think my approach would be to have a ported, NT-version of
wineserver.exe which just uses native functions of the OS instead of
emulating them over cygwin, which emul
On Wed, Jun 16, 2010 at 4:04 PM, Roderick Colenbrander
wrote:
> I don't expect Wine itself to ever work on cygwin. Last year I asked
> AJ about it and there are some special file handle features which are
> needed. This stuff is supported in SUA but at least in the Vista
> version this was broken.
I don't expect Wine itself to ever work on cygwin. Last year I asked
AJ about it and there are some special file handle features which are
needed. This stuff is supported in SUA but at least in the Vista
version this was broken. They MIGHT have fixed it for Win7, so if Wine
can work on Windows it w
(Sixth is someone writing a program loader for Wine on Cygwin. Seventh
is Win16 working in the Cygwin build.)
I suppose we can't have this in the 1.2 press release, really ;-)
- d.
Thanks to a few recent commits by AJ (and several commits over the
past months by others), wine now builds on Cygwin.
Not everything works, of course, but still a neat exercise in recursion.
I've put a screenshot of wine's notepad running on XP on bugzilla
(http://bugs.winehq.org/show_bug.cgi?id=
I think on most shells, you need to backslash escape the "*" - i.e.
yum install mingw32\*
Just to cover all grounds, I came across the opensuse location of SuSE
cross-compiler recently on the mono web site. (search in http://www.go-mono.com
or www.mono-project.com) since win32 mono can be cro
Am Sunday 26 July 2009 01:53:46 schrieb King InuYasha:
> > > .section ".init","ax"
> > > yields
> > > a.0dtc3a.s: Assembler messages:
> > > a.0dtc3a.s:5: Error: junk at end of line, first unrecognized character
> > > is `"'
> > >
> > > Then there is:
> > > .hidden __wine_spec_nt_header
> > > =>
> >
If you are using Fedora, "yum install mingw32*" will install the whole
cross-compiling suite.
On Sat, Jul 25, 2009 at 6:39 PM, Austin English wrote:
> On Sat, Jul 25, 2009 at 12:36 PM, dominik wrote:
> > Hi all,
> > I've just tried to build wine on cygwin in orde
On Sat, Jul 25, 2009 at 12:36 PM, dominik wrote:
> Hi all,
> I've just tried to build wine on cygwin in order to build the test suite in
> order to maybe find out why some tests fail on my machine.
>
> configure runs reasonably well, but when the first dll is being built,
Hi all,
I've just tried to build wine on cygwin in order to build the test suite
in order to maybe find out why some tests fail on my machine.
configure runs reasonably well, but when the first dll is being built,
hell breaks loose.
The assembler files generated from the .spec files ar
Am Mittwoch 10 Januar 2007 16:53 schrieb Chetan Venkatesh:
> Basically, what we are trying to do is run native Windows applications on a
> remote X desktop; we feel that the best way to do this would be to use wine
> as a base to develop a Windows to X translator/mapping, and then export the
> X ca
I got a lot of people asking me to post details about our intended project.
Basically, what we are trying to do is run native Windows applications on a
remote X desktop; we feel that the best way to do this would be to use wine
as a base to develop a Windows to X translator/mapping, and then ex
I got a lot of people asking me to post details about our intended project.
Basically, what we are trying to do is run native Windows applications on a
remote X desktop; we feel that the best way to do this would be to use wine
as a base to develop a Windows to X translator/mapping, and then ex
Am Dienstag 09 Januar 2007 19:41 schrieb Chetan Venkatesh:
> My company is looking for experienced Wine Developers to work on a
> commercial Open Source Project involving getting wine working under cygwin
> and Windows. Can anyone point me to the right mailing list / forum to make
> a posting at o
Hello Chetan,
I believe this link will be of help : http://www.codeweavers.com/services/
Regards,
Tom
On 1/9/07, Chetan Venkatesh <[EMAIL PROTECTED]> wrote:
My company is looking for experienced Wine Developers to work on a
commercial Open Source Project involving getting wine working under cy
My company is looking for experienced Wine Developers to work on a
commercial Open Source Project involving getting wine working under cygwin
and Windows. Can anyone point me to the right mailing list / forum to make
a posting at or can interested developers contact me please -
[EMAIL PROTECTED]
Hi Hans,
> Wait, I see now that there's another use of .previous which is protected
> differently. The path below may solve your problem.
thanks - I am now using the following change:
Changelog:
Don't use ".previous" for MinGW and Cygwin builds
Index: port.h
==
On Tuesday 5 October 2004 10:09, Hans Leidekker wrote:
> What compiler/platform are you on? This code is protected like this:
>
> #if defined(__GNUC__) && !defined(__MINGW32__) && !defined(__APPLE__)
>
> So if you're on Cygwin we may need to add && !defined(__CYGWIN__) or
> whatever is the appr
On Tuesday 5 October 2004 08:37, Martin Fuchs wrote:
> I tried building from the top, from libs/wine/, libs/port/, from some
> dlls/... and programs/... directories.
>
> When building from the top, I am getting:
>
> make[1]: Entering directory `/home/cvs/wine/libs'
> make[2]: Entering directory
> It looks like you are mixing includes from Wine and Mingw, that's not
> going to work well. My guess is that you didn't run make from the
> top-level directory, so Wine didn't get a chance to build its includes
> and Mingw falls back to the w32api ones.
I tried building from the top, from libs/w
"Martin Fuchs" <[EMAIL PROTECTED]> writes:
> when trying to compile WINE using Cygwin I am getting errors such as: (this example
> for wine/programs/notepad)
>
> gcc -c -I. -I. -I../../include -I../../include -I../../include/msvcrt
> -DNO_LIBWINE_PORT -D_REENTRANT -Wall -pipe -mprefe
> rred-sta
On Mon, 2004-10-04 at 15:47, Martin Fuchs wrote:
> Compiling...
> comctl32undoc.c
> d:\wine-msvc\include\windows.h(23) : fatal error C1189: #error : Wine should not
> include windows.h internally
>
> This all worked some months ago.
> Can someone explain, what's wrong here?
I think the order of
Hello,
when trying to compile WINE using Cygwin I am getting errors such as: (this example
for wine/programs/notepad)
gcc -c -I. -I. -I../../include -I../../include -I../../include/msvcrt
-DNO_LIBWINE_PORT -D_REENTRANT -Wall -pipe -mprefe
rred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wp
I wont believe any word that comes from an anonymous mail.
Alexandre, shouldnt we close this subject ?
=
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
ICQ #170597259
Say NO to software patents
Dites NON aux brevets logiciels
"You believe it's the year 1984, when in fact, it
--- Anonymous <[EMAIL PROTECTED]> wrote:
>
> I got cygwin to compile wine to the point where wine-install tried to
> run regedit on winedefault.reg.
>
> I should have been paying closer attention.
>
> The good news is that the wine regedit.exe works like a charm. The
> bad news is that it overw
I got cygwin to compile wine to the point where wine-install tried to run regedit on
winedefault.reg.
I should have been paying closer attention.
The good news is that the wine regedit.exe works like a charm. The bad news is that
it overwrote my actual windows registry with the bunk values in
30 matches
Mail list logo
