On Wed, Dec 2, 2009 at 11:43 AM, David Anderson wrote:
> I am trying to get the tests to run before I submit a patch to
> shdocvw/webbrowser.c. My first attempts to get the tests to run.
>
> This morning I did
> cd /home/davea/winebld/wine
> git fetch; git rebase origin # make sure you'r
>I am trying to get the tests to run before I submit a patch to
>shdocvw/webbrowser.c. My first attempts to get the tests to run.
>
>This morning I did
>cd /home/davea/winebld/wine
>git fetch; git rebase origin # make sure you're up to date
>./configure && make depend && make # rebuild
I am trying to get the tests to run before I submit a patch to
shdocvw/webbrowser.c. My first attempts to get the tests to run.
This morning I did
cd /home/davea/winebld/wine
git fetch; git rebase origin # make sure you're up to date
./configure && make depend && make # rebuild the tr
2008/10/15 Dmitry Timoshkov <[EMAIL PROTECTED]>:
> "Reece Dunn" <[EMAIL PROTECTED]> wrote:
>
>> When building the setupapi tests with VC9 and the MSVC headers (Vista
>> version) after using msvcmaker, I get the following output:
>>
>> 2>-- Build started: Project: setupapi_test, Configuration: D
"Reece Dunn" <[EMAIL PROTECTED]> wrote:
> When building the setupapi tests with VC9 and the MSVC headers (Vista
> version) after using msvcmaker, I get the following output:
>
> 2>-- Build started: Project: setupapi_test, Configuration: Debug
> MSVC Headers Win32 --
> 2>Linking...
> 2>mis
When building the setupapi tests with VC9 and the MSVC headers (Vista
version) after using msvcmaker, I get the following output:
2>-- Build started: Project: setupapi_test, Configuration: Debug
MSVC Headers Win32 --
2>Linking...
2>misc.obj : error LNK2019: unresolved external symbol _MyFr
Well, I have researched a bit error code -1073741819=0xc005
This a status_no_access violation, in winetest we should say the test
crashed message
On 10/27/07, Robert Shearman <[EMAIL PROTECTED]> wrote:
> Vijay Kiran Kamuju wrote:
> > Hi,
> >
> > I have been looking into http://test.winehq.org/
Vijay Kiran Kamuju wrote:
> Hi,
>
> I have been looking into http://test.winehq.org/data/.
> And I have got a question, when i saw the test data.
> Why do some tests do not return the data about tests they haven't run/skipped.
> They spew messages something like below:
>
> mapi32:prop start dlls/ma
Hi,
I have been looking into http://test.winehq.org/data/.
And I have got a question, when i saw the test data.
Why do some tests do not return the data about tests they haven't run/skipped.
They spew messages something like below:
mapi32:prop start dlls/mapi32/tests/prop.c 1.20
mapi32:prop done
Hi Paul,
--- Paul Vriens <[EMAIL PROTECTED]> wrote:
> I will give it a try. Is it OK to submit patches to the tests first
> (with todo_wine maybe) before I get into the fixing of Wine?
Yep, with todo_wine is fine.
--Juan
__
Do you Yahoo!?
Yaho
On Sat, 2005-01-29 at 18:29, Juan Lang wrote:
> > What's the best approach in this?
> > - fix Wine (but what should be the correct returned buffer?)
>
> Definitely fix Wine. Hopefully there isn't an app that depends on one
> behavior under Windows 98, and a different one under Windows XP. It's
>
> What's the best approach in this?
> - fix Wine (but what should be the correct returned buffer?)
Definitely fix Wine. Hopefully there isn't an app that depends on one
behavior under Windows 98, and a different one under Windows XP. It's
perhaps less likely because Wine's implementation isn't c
Hi,
I've been testing some of these test extensively and can make them pass
on all the windows versions I have running. Doing this however means it
breaks the wine test.
An example is:
/*
* string grows during expanding
* dwSize is larger then the size of part before the backslash but
smaller
13 matches
Mail list logo
