back. In their arrogance, they never
even consider that one might want to restrict their ability
to change things to that which belongs to a single user.
A very unfortunate trend...
cdr
Troy Rollo wrote:
Also, if the application is testing for Wine, why not do a Winelib port?
Single sorce to maintain, single binary to distribute.
cdr
imarily for the users who will want to run
an application that the application vendor would like to prevent from
running under anything but MS Windows.
cdr
Felix Nawothnig wrote:
cdr wrote:
much appreciated, cdr
Now... would you tell us what the misbehaviour in Wine is your
application suffers from?
Since bitblt isn't exactly rocket science this one should be easy to
fix... (no?)
It is on my "todo" list. But you must
Dimi Paun wrote:
if you *really* want to do it:
-- at compile time:
#ifdef __WINE__
#endif
-- at runtime:
if( GetProcAddress(LoadLibrary("kernel32"), "wine_get_unix_file_name")
{
.
}
much appreciated, cdr
more I'll be able to make my Win32 apps available to Linux users.
(int WinelibVersion(); that returns nn - Please, please...)
cdr
what
you want for a 'true' Linux app.
Should one expect read/write access to memory-mapped files
to be faster if it is native Linux? (I must say I am impressed
by the fact that Win32 memory-mapped file access works as
well under wine as it does).
cdr
While testing my Win32 application under wine, I came to the
conclusion that some bit-blit ops behave differently from
when the same code is running under native Windowds. While
the subject will be researched further, as a stop-gap measure
I have a need to detect - from within my application - tha
Dimi Paun wrote:
> That's fine it's supposed to do so. But it's also supposed to
> create a 'type' executable too (a batch file really).
This is where I was (obviously) confused, all I can say
in my defence is that Winelib User's Guide in "Getting started"
implies that:
(...
You are done! Now
Dimi Paun wrote:
From: "cdr" <[EMAIL PROTECTED]>
Mkefile generated by winemaker creates type.exe.so; where I
would expect either type.exe or simply type. What am I missing?
Is the Makefile using winegcc to compile the app?
If so, you should get 'type' as the execu
I am at the first stages of setting up my winelib development, and
am attempting to build a simple app (named "type").
Mkefile generated by winemaker creates type.exe.so; where I
would expect either type.exe or simply type. What am I missing?
tia, cedar
11 matches
Mail list logo
