On Tue, Dec 1, 2015 at 2:17 AM, Nikolay Sivov nsivov@codeweavers.com wrote:
On 30.11.2015 21:03, Bruno Jesus wrote:
I had a small problem tough, in the compiled version of the program printf works in wine but does not in Windows (no, not a buffering problem, fflush does not help). In Windows not a single line is printed to the console, maybe that is correct, I don't know so I changed to output a text file instead.
Even if it's not possible for some reason, you can always make it write to a file directly.
Yes, that is what the test is doing by using fprintf to output.txt.
The question that remains, how to submit a patch that was tested with an external (not wine test suite) program? (test attached)
Currently the only way is to submit without it, and mention it in a mail. Hopefully in the future tests could be kept in similar separate repository, and built regularly.
I attached a zip file to the bug containing the test source, compiled 16-bit exe and outputs before and after the test. The output is only loosely based in wine test suite.