Hi,
I have a suggestion about wineTestBot. It's maybe the wrong place but I'm quite sure interested people read wine-devel.
I think it would be great if we could not only run tests (as it already does) but also check if a patch does not break wine (on minGW, on cygwin or on MAC for instance).
Thus, we could choose a kind of WINEBUILD VM to tell wineTestBot to only compile wine with our patch.
Currently, I can't compile on Linux and cygwin is very slow. So it would make my life easier if I could rely on wineTestBot...
Comments are welcome Thanks
Alexandre Goujon ale.goujon@gmail.com wrote:
Currently, I can't compile on Linux and cygwin is very slow. So it would make my life easier if I could rely on wineTestBot...
For any productive Wine development you need not only working compiling environment, but a working Wine binary, to run at least 'make test'.
Dmitry Timoshkov wrote
For any productive Wine development you need not only working compiling environment, but a working Wine binary, to run at least 'make test'.
Ok so I could not run any test until compiling on cygwin works. But the idea was to be able to remotly compile wine with some of our patches applied.
I was told "you can't do that, it will break minGW". The WINEBUILD VM exists but we can't use it (or tell me how to do that)
Of course I could install MinGW on my PC too...
Alexandre Goujon ale.goujon@gmail.com wrote:
For any productive Wine development you need not only working compiling environment, but a working Wine binary, to run at least 'make test'.
Ok so I could not run any test until compiling on cygwin works.
Even if compiling under Cygwin works, the tests still require running them under Wine, and Wine can't run under Cygwin (and most likely will never be able to).
Patchwatcher is suppose to sort of do this. It only works for linux, not other systems, but it will not only check your patch against compiling but also against the test suit and mark and regressions.
I didn't know this tool. It looks quite interesting.
Thanks again for your advices