Home / Browse / MinGW - Minimalist GNU for Windows / Mail / Archive

MinGW - Minimalist GNU for Windows

Email Archive: mingw-users (read-only)

Re: [Mingw-users] Some questions on __imp_ prefix, and other linking problems

From: 俞晓磊 <elioxia@gm...> - 2011-03-28 01:55

Hello John
Thanks for your information.

>
> What does `nm libEGL.a` say? Are you linking directly to the DLL or are you
> using import libraries?
>

Yes, I am linking to libEGL.dll and libGLESv2.dll.

>
> There may be an easier way, but you can create aliases in the .DEF file:
> EXPORTS
> eglBindAPI=eglBindAPI@...
> eglBindTexImage=eglBindTexImage@...
>
> or something similar. Again, I think that the MinGW FAQ will help.
>
>  <http://InboxLight.aspx?n=454371129#>

I followed MinGW faq and produced .a files from the dlls. Things seem to be
fine.
But I still cannot found any documentation on *_imp_* prefix. The faq does
mention __stdcall prefix, but it is for msvc.
Best Regards

Thread View

Thread	Author	Date
Re: [Mingw-users] Some questions on __imp_ prefix, and other linking problems	俞晓磊 <elioxia@gm...>

Re: [Mingw-users] Some questions on __imp_ prefix, and other linking problems

From: John Brown <johnbrown105@ho...> - 2011-03-28 05:18

Attachments: Message as HTML

Hello 俞晓磊

> I followed MinGW faq and produced .a files from the dlls. Things seem to be fine.
> But I still cannot found any documentation on *_imp_* prefix. The faq does
> mention __stdcall prefix, but it is for msvc.

I gave you wrong / incomplete information. Using stdcall causes the @n to be
added to function names. __declspec(import), which tells the compiler that the
function is imported from a DLL, is what adds the __imp_ prefix.

See http://support.microsoft.com/kb/132044 for more information.

Regards,
Alias John Brown.

Re: [Mingw-users] Some questions on __imp_ prefix, and other linking problems

From: Greg Chicares <gchicares@sb...> - 2011-03-28 13:15

On 2011-03-28 05:18Z, John Brown wrote:
> 
> I gave you wrong / incomplete information. Using stdcall causes the @n to be
> added to function names. __declspec(import), which tells the compiler that the
> function is imported from a DLL, is what adds the __imp_ prefix.

I see __imp_ symbols in code that I've linked directly to a dll,
with no __declspec decorations used anywhere, so I guess direct
linking generates them, too.

> See http://support.microsoft.com/kb/132044 for more information.

Also see:
  http://blogs.msdn.com/b/oldnewthing/archive/2006/07/27/679634.aspx

Re: [Mingw-users] Some questions on __imp_ prefix, and other linking problems

From: Earnie <earnie@us...> - 2011-03-28 13:46

俞晓磊 wrote:
> I followed MinGW faq and produced .a files from the dlls. Things seem to be
> fine.
> But I still cannot found any documentation on *_imp_* prefix. The faq does
> mention __stdcall prefix, but it is for msvc.

You don't need to create the .a, binutils will use the dlls directly to
get the import information.  You just need to make sure that ld can find
the dll.

I suggest following leads via
http://www.google.com/search?q=binutils+__imp_ for how/what information
on the *_imp_* prefix.

-- 
Earnie
-- http://www.for-my-kids.com