On Thursday 12 May 2005 23:00, Saulius Krasuckas wrote:
Changelog:
Don't import from ntdll.
Can someone explain me, please, where would atoi() function be linked now
to?
The native C library (glibc on Linux).
-Hans
Hi all,
please find attached my current work on this topic. It takes another approach
as Michael Lin's patches and in particular doesn't add any API.
I've already send the smaller of the two patches to wine-patches, so it may
well be that this one is already applied when you try the patches.
On Fri, 13 May 2005, Dimi Paun wrote:
On Thu, 2005-05-12 at 16:49 +0200, Francois Gouget wrote:
This patch adds the framework for translating Wine's documentation and
adds a translation of the FAQ to French as a demonstration.
No compressed patches, please.
I know, I only compressed it because of
On Fri, 13 May 2005, Martin Fuchs wrote:
Changelog
use macros for platform dependent temporary allocations
[...]
+#define TMP_ALLOC(s) HeapAlloc(GetProcessHeap(), 0, s)
+#define TMP_FREE(p) HeapFree(GetProcessHeap(), 0, p)
+#else
+#define TMP_ALLOC(s) alloca(s)
+#define TMP_FREE(p)
#endif
Why is
On Thu, 12 May 2005, Steven Edwards wrote:
[...]
But your defining UnixFSGetOpenFileNameW in the spec file so the import library
will still have
that function listed so if I link a dll to that import library its going to
fail on Windows even
if I am not calling that function.
No, that should not
On Fri, 2005-05-13 at 11:47 +0200, Francois Gouget wrote:
No compressed patches, please.
I know, I only compressed it because of the size.
Yeah, but that meant I couldn't read it most of the day, as
I couldn't decompress it. Plus it's a pain. Patches shouldn't
be too big to begin with, and
Jonathan Wilson wrote:
Its highly likely that GCC and WINE are already infringing on some
software patent somewhere (since its well nigh impossible not to in the
current patent everything you can climate inside a number of big
companies)
What makes this particular borland patent any different?
On Fri, 13 May 2005, Dimi Paun wrote:
[...]
The project is reasonably active. And it's just perl so installation is
pretty trivial. We could even stick it in a po4a/ directory in CVS and
use it from there.
Yeah, I think that's the way to go. We shouldn't make it a pain for
people to contribute.
On Thu, 12 May 2005, gslink wrote:
The whole business of software patents is very likely to explode at any time.
I assume this is somewhat related to the Winelib article on Slashdot:
Winelib Hobbled by Exception-Handling Patent
http://yro.slashdot.org/yro/05/05/12/1947213.shtml
If not I'll make
Why is this needed?
Doesn't HeapAlloc work on any 'Win32' platform?
I want to avoid calling heap allocation functions.
Using alloca() is slightly lighter.
Regards,
Martin
In
reality almost nothing of any importance currently runs on Wine without
some setup.
Any such setup is to work around wine bugs. The proper way to go about such
problems is to fix wine, not setup anything.
What you probably need to do is to experiment with
replacing some of the dlls or
Doesn't HeapAlloc work on any 'Win32' platform?
I want to avoid calling heap allocation functions.
Using alloca() is slightly lighter.
Please don't do that. It uglifies the code, and makes
it less reliable. alloca() is lighter but it's on the
stack, and I really doubt that yoy can measure
The best way to do that would be to do a vendor import. The way to do
that would be as follows:
True. There's no point to first add the Fr translation and then po4a
if the FR requires it. We need to decide if we are going to use it
or not. I have no experience with it, any other opinions out
On Friday 13 May 2005 15:09, Francois Gouget wrote:
* The Slashdot summary makes it sound like Wine is infringing on the
patent and that we will have to remove some code.
Wine duplicates many of the data structures in Windows which are described in
the patent. Code using the C syntax
Hi,
--- Francois Gouget [EMAIL PROTECTED] wrote:
No, that should not happen. If an application links with a library that
exports funcA() and funcB() but it only calls funcA(), then it will only
import funcA() and it will work on a system where that library only
exports funcA().
OK maybe I
What are the thoughts about this?
Having a winev4l seems like it would be the way to go.
There's a lot of good info in this message, maybe you
can create a page on the Wiki to capture all this stuff.
--
Dimi.
On Wed, 2005-05-11 at 14:38 -0600, Vitaliy Margolen wrote:
Is there a way of trapping and spitting to stdout all the window-related
event messages that are being sent to an app? Or do they not happen in
any kind of central enough place to do that? (I suppose it'd also be
useful to be able
Hi.
Martin Fuchs wrote:
Hi,
I want to merge some Robert Dickenson's version of winfile (derived from the
old winefile code in 2002) in the next time into winefile. At the same time I
want to keep the code it in sync between the ReactOS code base and Wine.
What do you think about splitting
When I tried to install Firefox 1.0.4 for Windows, I got the following
output in the shell window I started wine from.
[EMAIL PROTECTED]:~/Download/Software wine Firefox\ Setup\ 1.0.4.exe
fixme:win:SetWindowTextW cannot set text LExtracting of other process
window 0x7002e
Andrew wrote:
Firefox appeared to install correctly, but it won't start. Trying to
install under winedbg with WINDEBUG=+trace winedbg to terminate the
application after I typed next:
Hmm, works for me here. I assume you mean WINEDEBUG=, not WINDEBUG=.
And, do you mean WINEDEBUG=trace or
On Fri, 2005-05-13 at 22:43 +0200, Jacek Caban wrote:
We're planning to add a new explorer application.
Who's we?
--
Dimi Paun [EMAIL PROTECTED]
Lattica, Inc.
On Wed, 11 May 2005 23:01:17 +1200, Adrian Harvey wrote:
Well, I got some output at least! Never used strace before, but it
looks kinda like a +relay trace for the kernel :-)
Yep, that's exactly what it is :)
I also happened to be tailing the syslog (I was looking at something
22 matches
Mail list logo
