Re: [PATCH 1/2] gdi32: Add a string table resource for the translation.

[Alexandre Julliard]

Akihiro Sagawa <sagawa.aki(a)gmail.com> writes:
> @@ -1,7 +1,7 @@
>  EXTRADEFS = -D_GDI32_
>  MODULE    = gdi32.dll
>  IMPORTLIB = gdi32
> -IMPORTS   = advapi32
> +IMPORTS   = advapi32 user32

You don't want to import user32 from gdi32.

-- 
Alexandre Julliard
julliard(a)winehq.org

[PATCH 1/2] gdi32: Add a string table resource for the translation.

[Akihiro Sagawa]

On Tue, 18 Oct 2011 16:14:36 +0200, Alexandre Julliard wrote:
> Akihiro Sagawa <sagawa.aki(a)gmail.com> writes:
> > @@ -1,7 +1,7 @@
> >  EXTRADEFS = -D_GDI32_
> >  MODULE    = gdi32.dll
> >  IMPORTLIB = gdi32
> > -IMPORTS   = advapi32
> > +IMPORTS   = advapi32 user32
>
> You don't want to import user32 from gdi32.

LoadStringW is in user32.dll. Should I use DELAYIMPORTS instead?

-- 
Akihiro Sagawa

[PATCH 1/2] gdi32: Add a string table resource for the translation.

[Alexandre Julliard]

Akihiro Sagawa <sagawa.aki(a)gmail.com> writes:
> On Tue, 18 Oct 2011 16:14:36 +0200, Alexandre Julliard wrote:
> > Akihiro Sagawa <sagawa.aki(a)gmail.com> writes:
> > > @@ -1,7 +1,7 @@
> > >  EXTRADEFS = -D_GDI32_
> > >  MODULE    = gdi32.dll
> > >  IMPORTLIB = gdi32
> > > -IMPORTS   = advapi32
> > > +IMPORTS   = advapi32 user32
> >
> > You don't want to import user32 from gdi32.
>
> LoadStringW is in user32.dll. Should I use DELAYIMPORTS instead?

No, you should do it by hand using kernel32 resource functions. And you
should do that only when needed, not on every startup.

-- 
Alexandre Julliard
julliard(a)winehq.org