Re: api-ms-win-core-localregistry-l1-1-0: add stub dll

[Charles Davis]

On Jun 4, 2013, at 12:15 PM, Austin English wrote:
> diff --git a/dlls/api-ms-win-core-localregistry-l1-1-0/api-ms-win-core-localregistry-l1-1-0.spec b/dlls/api-ms-win-core-localregistry-l1-1-0/api-ms-win-core-localregistry-l1-1-0.spec
> new file mode 100644
> index 0000000..cc15d4e
> --- /dev/null
> +++ b/dlls/api-ms-win-core-localregistry-l1-1-0/api-ms-win-core-localregistry-l1-1-0.spec
> @@ -0,0 +1,40 @@
> +@ stub RegCloseKey
> Why don't you just forward them to their implementations in advapi32? Is there something oddly different about these functions that I don't know about?

Chip

api-ms-win-core-localregistry-l1-1-0: add stub dll

[Austin English]

On Tue, Jun 4, 2013 at 5:05 PM, Charles Davis <cdavis5x(a)gmail.com> wrote:
> On Jun 4, 2013, at 12:15 PM, Austin English wrote:
> > diff --git a/dlls/api-ms-win-core-localregistry-l1-1-0/api-ms-win-core-localregistry-l1-1-0.spec b/dlls/api-ms-win-core-localregistry-l1-1-0/api-ms-win-core-localregistry-l1-1-0.spec
> > new file mode 100644
> > index 0000000..cc15d4e
> > --- /dev/null
> > +++ b/dlls/api-ms-win-core-localregistry-l1-1-0/api-ms-win-core-localregistry-l1-1-0.spec
> > @@ -0,0 +1,40 @@
> > +@ stub RegCloseKey
> > Why don't you just forward them to their implementations in advapi32? Is there something oddly different about these functions that I don't know about?
>
> Chip

Michael pointed that out as well, fixed in try 2 sent earlier today.

--
-Austin