I think you can just compile and run it with visual C++ as a standalone app, with the right commandline options to the compiler. Let's see: try the instructions here: http://www.winehq.com/hypermail/wine-devel/2005/05/0865.html
You can also build with the wine build system and then run the executable with a single commandline option giving the name of the test to run. Better ask on wine-devel, I have to run.
On 6/2/06, EA Durbin ead1234@hotmail.com wrote:
How does one use the test application in the msi/tests folder?
I know you run it with wine, but without looking through all of the code in the application to determine this could you maybe advise me what it expects for arguments, or how to work with it?
Do you pass it an misdatabase, and a DB argument, or how does this utility work?
I don't usually hack in C, but im somewhat capable. I could write a mean Hello World Application back in college. My day usually consists of parsing data with PERL, but that doesn't mean I can't pick up C again.
I'd appreciate it if you focused some energy on it, but I would also like to know how it works so I can contribute in the future.
From: "Dan Kegel" dank@kegel.com To: wine-devel wine-devel@winehq.org Subject: re: test case for MSI problem in America's Army installer Date: Fri, 2 Jun 2006 07:06:30 -0700
Mike M. wrote:
[America's Army install crashes, see http://bugs.winehq.org/show_bug.cgi?id=5139 ]
This is as close as I will be able to come to including a test case, as this is how I obtained my results.
If you want me to fix the problem, please submit a regression test to wine-patches with a todo_wine{} around the code that doesn't work.
If that's too hard for EA (he admits he's not a C hacker), maybe I can focus some energy on it...
- Dan