I think you can't depend on files existing in the source directory; you have to create them yourself (e.g. from a hex array in your source). Otherwise the unified winetest app that we use for semiautomated remote windows testing by users won't work.
But if, say, WINETEST_INTERACTIVE is set, you can still use test.avi in the local directory instead of creating one.
On Thu, Apr 03, 2008 at 06:14:03PM -0700, Dan Kegel wrote:
I think you can't depend on files existing in the source directory; you have to create them yourself (e.g. from a hex array in your source). Otherwise the unified winetest app that we use for semiautomated remote windows testing by users won't work.
But if, say, WINETEST_INTERACTIVE is set, you can still use test.avi in the local directory instead of creating one.
It doesn't depend on any files anywhere at runtime. The file is compiled into the executable as a resource and the resource is extracted to a temp file at runtime, so the executable is all you need to run the test.
On Thu, Apr 3, 2008 at 7:17 PM, Dan Hipschman dsh@linux.ucla.edu wrote:
It doesn't depend on any files anywhere at runtime. The file is compiled into the executable as a resource and the resource is extracted to a temp file at runtime, so the executable is all you need to run the test.
Well, foo. I stand corrected. Sorry for the noise!
-
Dan Hipschman -
Dan Kegel