Hello Kris,
2008/5/14 Kris Moore <[EMAIL PROTECTED]>:
>
> I'm trying to get Wine to compile with HAL support on FreeBSD, and
> running into this error:
>
> > checking dbus/dbus.h usability... yes
> > checking dbus/dbus.h presence... yes
> > checking for dbus/dbus.h... yes
> > checking hal/libh
Sergey Khodych wrote:
>> To reply to myself. I've missed the fact that if the requested format
>> is the
>> same as Wine's internal format it will be a simple memcpy. I did not
>> want to
>> penalize most dinput applications that just use default keyboard
>> format (array
>> of 256 bytes).
>>
>
Oddly, I only see
shelllink.c:90: Test succeeded inside todo block: SHILCreateFromPath
failed (0x)
shelllink.c:194: Test succeeded inside todo block: path_to_pidl
returned a NULL pidl
shelllink.c:214: Test failed: GetPath returned 'C:\nonexistent\file'
shelllink: 190 tests executed (2 marke
I'm trying to get Wine to compile with HAL support on FreeBSD, and
running into this error:
> checking dbus/dbus.h usability... yes
> checking dbus/dbus.h presence... yes
> checking for dbus/dbus.h... yes
> checking hal/libhal.h usability... yes
> checking hal/libhal.h presence... yes
Hmm. I just tried running Photoshop CS2 trial and Photoshop 5.5 trial,
and both failed on current wine.
CS2 complained "not enough DOS memory",
and 5.5 complained
lcms: Error #12288; Too many tags (2025813777)
PS6 works, though.
Eric Pouech escribió:
Alex Villacís Lasso a écrit :
Even though the code freeze is still in effect, I post this so that it
will be reviewed. For more information, see bug #12311.
Changelog:
* richedit: empty text should result in a scroll range of 0.
* Tests for this behavior.
---
> To reply to myself. I've missed the fact that if the requested format is
> the
> same as Wine's internal format it will be a simple memcpy. I did not
> want to
> penalize most dinput applications that just use default keyboard format
> (array
> of 256 bytes).
>
What do you think about using c
Hi Folks,
We have provisionally set Wineconf for the weekend of September 27/28 in Saint
Paul, Minnesota.
The Wine conference is open to all. We host 2 days of informal sessions
to discuss technical issues related to Wine development. We'll likely also
have a celebration of Wine 1.0, and other
On Wed, May 14, 2008 at 5:48 AM, Kornél Pál <[EMAIL PROTECTED]> wrote:
> If contributors agree only the current version will be MIT/X11 licensed.
>
> But I would like to know if the Wine community is willing to license msvcrt
> under MIT/X11 after that in the future in Wine's source repository to h
Kai,
that test will always fail on some systems. How about this:
just test for whether that function completes at all, rather
than testing for success.
- Dan
Ahh. Here you go.
-Austin
On Wed, May 14, 2008 at 4:29 AM, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> "Austin English" <[EMAIL PROTECTED]> writes:
>
>> Anything wrong with this patch?
>>
>> http://www.winehq.org/pipermail/wine-patches/2008-May/054794.html
>
> It's not a valid git patch.
>
>
> On Wed, May 14, 2008 at 6:26 AM, Pavel Troller <[EMAIL PROTECTED]> wrote:
> > Hi!
> > I have a very good news today! I tested the current wine git and I've found
> > that it works again in the case of a device mentioned above! It's really
> > good,
> > because it didn't work in 0.9.61 and using
On Wed, May 14, 2008 at 6:26 AM, Pavel Troller <[EMAIL PROTECTED]> wrote:
> Hi!
> I have a very good news today! I tested the current wine git and I've found
> that it works again in the case of a device mentioned above! It's really good,
> because it didn't work in 0.9.61 and using 0.9.40 was not
Vitaliy Margolen wrote:
> Sergey Khodych wrote:
>>> Any particular reason for this? Do you have a program that sets different
>>> data format? The reason I ask - copying 256 bytes is much faster then
>>> iterating over the whole data format and copying one byte at a time.
>>>
>> A possibility of
> From: Steven Edwards
>> So the question is: If the current authors permit to make msvcrt MIX/X11
>> licensed would it be possible to make Wine's msvcrt MIT/X11 licensed for
>> future releases as well (no legal question but philosophical)?
>
> You will need to review the git history and contact
On Wed, May 14, 2008 at 8:37 AM, Kornél Pál <[EMAIL PROTECTED]> wrote:
> So the question is: If the current authors permit to make msvcrt MIX/X11
> licensed would it be possible to make Wine's msvcrt MIT/X11 licensed for
> future releases as well (no legal question but philosophical)?
You will
> Pavel wrote:
> > I have to use wine-0.9.40 to communicate with a device
> > in my work (simple text-based command-reply communication),
> > any wine newer than say 0.9.50 doesn't work, the communication times out.
> > ... I will try to dig into the driver and search for the bugs there.
> > One of
> From: Dan Kegel
>> Also note that Mono's Class Library is licensed under MIT/X11 because
>> inlining (done by the runtime) may be incompatible with GPL that would
>> not
>> allow non-GPL programs to be executed within Mono. Would it be possible
>> to
>> have a MIT/X11 licensed msvcrt?
>
> That'
http://bugs.winehq.org/show_bug.cgi?id=9376
People who generate annoying cookiecutter Flash web sites
can now migrate to LInux with confidence :-)
On Wed, May 14, 2008 at 2:37 AM, Kornél Pál <[EMAIL PROTECTED]> wrote:
> Because mixed-mode (there is no pure managed version) msvcrts require
> Managed C++ and C++/CLI and there is no open source compiler supporting any
> of these so MS compilers would be required.
Bleah. Well, you gotta do wha
Hi,
> From: Dan Kegel
> But Wine has its own increasingly useful implementation of msvcrt,
> at least the part that uses the C api. (The C++ api is difficult for us
> because it has to be written in C; g++ uses a different ABI than Microsoft
> C++.)
>
> Perhaps, once we work the kinks out, Mono
"Austin English" <[EMAIL PROTECTED]> writes:
> Anything wrong with this patch?
>
> http://www.winehq.org/pipermail/wine-patches/2008-May/054794.html
It's not a valid git patch.
--
Alexandre Julliard
[EMAIL PROTECTED]
22 matches
Mail list logo
