[msi OLE automation] Re: msi patches info pls
mk144210 at bcm.tmc.edu
Wed Apr 4 16:45:33 CDT 2007
On Tue, 2007-04-03 at 16:54 +0100, Robert Shearman wrote:
> Misha Koshelev wrote:
> > On Fri, 2007-03-09 at 17:27 +0100, Alexandre Julliard wrote:
> >> Sorry for the lack of response, I'm currently waiting for our lawyers
> >> to determine if it's ok to use code based on an oleview dump of a
> >> native typelib, as that situation is not clear from a copyright
> >> POV. I'm afraid I can't do more until they come to a conclusion on
> >> that point.
> > So it looks like I will have some free time soon (hopefully) and will be
> > able to redo the "IDL" file properly (also another Vector NTI/Linux user
> > has offered up his help). However, I wanted to double check the "proper"
> > way to make such a file as I know this is what is important in copyright
> > (the process, such as dirty-clean room, vs the actual end result).
> What you can do is describe the IDL file in plain English (e.g. the
> first method is called "Foo" and takes an in argument of type VARIANT
> followed by an out argument of type VARIANT *...) and send it to
> wine-devel. Then me or someone else can go along and write the IDL out
> based on your description alone, and you can resubmit the remaining
> parts of your patches.
> Hope this helps,
That helps a lot. I think I should have that done sometime this month,
hopefully sooner rather than later (I am going to be busy this month but
not as busy as last month).
More information about the wine-devel