"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> I offered a proposed solution to a whole class of failures and you
> shot it down saying it was the wrong solution for standalone builds. I
> addressed that, your answer is now "If some test fails that doen't
> mean that the build is broken". But I do
On Mon, May 19, 2008 at 1:47 AM, Dmitry Timoshkov
<[EMAIL PROTECTED]> wrote:
> Carefully investigating each test failure one by one as Dan does is
> the right approach IMO, flaming on wine-devel is not.
Sorry if I went a little too flamish in my reply earlier. I did not
mean to imply your point of
"Rolf Kalbermatter" <[EMAIL PROTECTED]> wrote:
> The test framework should not only help avoiding regressions for the
> VERY active developers but allow anyone working on Wine in one way or
> the other to have some confidence that he got it to build right. It's
> what I usually do when installing
Hey Dmitry,
I'd like to reply point by point but Rolf's message sums up the way I
feel about the framework. I've avoided using it more than I could have
and am going to be doing a lot more work with it in the future so I
have in interest in seeing it pass 100% on more than just Julliards
box. I di
Please both calm down a bit.
<[EMAIL PROTECTED]> wrote:
>"Steven Edwards" <[EMAIL PROTECTED]> wrote:
>><[EMAIL PROTECTED]> wrote:
>>> Not everyone supposed to run the Wine tests, only those do who
>>> *really* can comprehend the results and able to do something with them.
>>
>> NO. Everyone that
"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> On Sun, May 18, 2008 at 10:02 PM, Dmitry Timoshkov
> <[EMAIL PROTECTED]> wrote:
>> How much tests do you usually build, and how often? I do it routinely
>> almost every day on a separate Windows machine by copying single .c
>> files and compiling them
On Sun, May 18, 2008 at 10:02 PM, Dmitry Timoshkov
<[EMAIL PROTECTED]> wrote:
> How much tests do you usually build, and how often? I do it routinely
> almost every day on a separate Windows machine by copying single .c
> files and compiling them as standalone tests. I don't see any rationale
> beh
Hi Bob,
could you open a bug at bugs.winehq.org, and put everything you wrote
in your email in the description? You might have more luck getting
followup that way.
Thanks,
--Juan
"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> On Sun, May 18, 2008 at 2:52 PM, Kai Blin <[EMAIL PROTECTED]> wrote:
>>> <[EMAIL PROTECTED]> wrote:
>>> > That will make compiling tests under Windows even more cumbersome than
>>> > it is now, there is no such a thing as config.h under Windows.
>>>
>>
On Sun, May 18, 2008 at 2:52 PM, Kai Blin <[EMAIL PROTECTED]> wrote:
>> <[EMAIL PROTECTED]> wrote:
>> > That will make compiling tests under Windows even more cumbersome than
>> > it is now, there is no such a thing as config.h under Windows.
>>
>> What are you talking about? If you use mingw or ms
Dear Wine developers,
Starting from version 2.x the libtool would like the create an
environment where user to be able to run win32 programs.
The former version 1.5x has this capability, but with some limitation in
case of cross-compilation environment.
The current libtool HEAD revision contain co
Am Sonntag, 18. Mai 2008 18:11:35 schrieb Roderick Colenbrander:
> Hi,
>
> This patch is a workaround for a severe WineD3D issue which is too much
> work and to risky to fix properly during the code freeze. It fixes drawing
> issues in GTR2, Suppreme Commander, Call of Duty 2 Call of Duty 4 and
> l
On Sunday 18 May 2008 19:30:18 Steven Edwards wrote:
> On Sun, May 18, 2008 at 2:30 AM, Dmitry Timoshkov
>
> <[EMAIL PROTECTED]> wrote:
> > That will make compiling tests under Windows even more cumbersome than
> > it is now, there is no such a thing as config.h under Windows.
>
> What are you talk
On Sun, May 18, 2008 at 2:30 AM, Dmitry Timoshkov
<[EMAIL PROTECTED]> wrote:
> That will make compiling tests under Windows even more cumbersome than
> it is now, there is no such a thing as config.h under Windows.
What are you talking about? If you use mingw or msvc to build the
tests in tree the
On Saturday 17 May 2008 01:01:15 Andrew Eleneski wrote:
> For my box I am running Kubuntu Hardy with Ati driver version 8.4. I see
> I crashed on the d3d9:stateblock, and have quite a few failures in the
> d3d9:visual area.
See http://wiki.winehq.org/MakeTestFailures
Cheers,
Kai
--
Kai Blin
Wor
15 matches
Mail list logo
