dev-cpp-users

[Dev-C++] mingw, cygwin, msvc,...

[<gen...@ya...>]

afaik, gcc (mingw/cygwin) *cannot* use msvc import
libs. using a tool called 'impdef', you can however
generate a gcc-style import lib *from a dll* compiled
with msvc.

when building libs for gcc (mingw/cygwin), you end up
with a file with an extension of '.a', not one of
'.lib', which is what's generated by
msvc/borland/watcom(for the first two, i'm sure, but
not for the last).

i'm not even sure that borland and msvc import libs
are compatible, since when i was using borland to
compile some msdn examples, there were runtime errors.
apparently, borland expected some OWL (object windows
library) info, and terminated the apps with a 'xyz
missing in abc' type of message.

for the python thingy, i've used dynamic linking to
import functions from the dll, but it's a pain, since
you have to consult the header files contantly and
create your own typedefs, etc, which of course takes
the fun out of learning how to embed python.

you can take a look @ my blog and see more about the
python on windows thing: http://phoenix.cowblock.net


	
	
		
___________________________________________________________
WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe Awards  www.yahoo.co.uk/internetcafes 

Re: [Dev-C++] mingw, cygwin, msvc,...

[Daniel K. O. <dan...@ya...>]

Oladipo Odumosu wrote:

>afaik, gcc (mingw/cygwin) *cannot* use msvc import
>libs. using a tool called 'impdef', you can however
>generate a gcc-style import lib *from a dll* compiled
>with msvc.
>  
>

Actually, you *can* use a MSVC dll or a MSVC lib, if it is a plain C 
library. With a dll you can even link directly to it, no need to use 
import libs. The problem is only with lib/dlls written in C++; those 
won't work even with impdef, because MSVC's C++ implementation is 
different from MinGW.



Daniel K. O.