Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > Compilers LCC > lccwin32's im**...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 1 Topic 1033 of 1058
Post > Topic >>

lccwin32's im****t library function..

by "copx" <copx@[EMAIL PROTECTED] > Apr 18, 2008 at 06:12 AM

I build DLLs using MS VC6 to ****eld tmy programs from the uglyness that is 
Windows/C++ (DLL offers C interface to C++ Windows stuff like SAPI 5). I
can 
use these DLLs with mingw after im****ting the related im****t library. 
However, it did not work with lccwin32 - unresolved references (compiler 
cannot find any DLL functions). After a lot of head scratching I attempted

to actually use my DLLs with VC6 (instead of just using that compiler to 
build them): same problem.
I eventually figured out that the problem could be fixed by specifing the 
calling convention in the header file. I use the __stdcall convention for 
the DLLs.
Now I wonder: why can mingw figure out the calling convention of the DLL 
without any compiler specific dressing but VC6/lcc cannot?
Isn't the calling convention info stored in the lib? Do I need to turn on 
some special switches to built MS im****t libs which work even without 
specifying the calling convention in the header?
I ask because I want to use the same header for all compilers I use and 
stuff like "__stdcall" breaks GCC (uses different syntax for specifying 
calling conventions).
 




 1 Posts in Topic:
lccwin32's import library function..
"copx" <copx  2008-04-18 06:12:27 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Sun Jul 6 19:21:11 CDT 2008.