> > I currently only have an all pointer (NULL, NOACCESS, READWRITE,
> > READWRITE) test, but writting more tests is easy.
> 
> I'll have to look at the code to see what you mean... :)

What I meant is that for a function say
        @ stdcall Foo(ptr long ptr long) Foo
winapi_test generates the following tests
        Foo(NULL, 0, NULL, 0);
        Foo(NOACCESS, 0, NULL, 0);
        Foo(READWRITE, 0, NULL, 0);
        Foo(READONLY, 0, NULL, 0);
        ...
        Foo(NULL, 0, READONLY, 0);
        Foo(NOACCESS, 0, READONLY, 0);
        Foo(READWRITE, 0, READONLY, 0);
        Foo(READONLY, 0, READONLY, 0);
and then winapi_xref can compare the results of the functions.
 
> > Hmm. I guess I could do some tricks with LD_LIBRARY_PATH. Of course
> > Corel Wine's (libwine.so) is not binary compatible with the current
> > version of Wine so that won't work either.
> 
> We are working to change this (we are trying to merge after all)

Good, that would make things considerably easier.

The generated WineLib application only links with libwine.so,
it uses LoadLibrary and GetProcAddress to access the functions
in other dlls so only libwine.so need to be compatible as far
as winapi_test's generate WineLib application is concerned.

By installing them diffrent versions in say
        /usr/local/lib/wine/corel
        /usr/local/lib/wine/current
we could just do specify the right LD_LIBRARY_PATH
for each case and everything would work with just
a few minor change to winapi_xref.

> > Wait a minute. What does the Corel Linux distribution do?
> > IIRC is possible to have both Corel Wine and Wine installed
> > at the same time. Or is that just a gross hack that is Corel
> > Office specific?
> 
> We have munged the configure scripts to install our versions 
> of wine whereever we want so a generic install will not be 
> smashed installing a Corel application.  Some people we know 
> would be unhappy
> about that sort of thing...

Yes, I certainly would. :-)
 
> > I will see if I find time to make a prerelease of winapi_test
> > later today. At least something useful currently works,
> > eventhough it still is a gross hack (slow and bloated).
> 
> I have seen the post,  I will look at it RSN.

Good, but remember it is a gross hack so it might
not be obvious how things work. Please ask whatever
you like.

Reply via email to