Re: Problem with QTAda 3.0 and QTCore4.dll on Windows

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Thu, 7 Jan 2010 14:11:37 -0800 (PST), Vadim Godunko wrote:

> On Jan 7, 1:59�pm, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
> wrote:
>> On Thu, 07 Jan 2010 08:19:17 +0100, Per Sandberg wrote:
>>> The core reason is that the Binary Interface specific the name-mangling
>>> in C++ is different between gcc and MSVC, on top of that the
>>> documentation in the MSVC case is "sparse".
>>
>> That should not be a problem in case of C. One should only make a choice
>> between stdcall and cdecl convention when you make a call from Ada. I guess
>> Qt has plain C interface? Then what happens inside of it is no matter.
>>
> Qt is pure C++ library, there is no C interface provided by it.

Well, the question is whether the interface uses virtual functions and
classes you have to derive from. That would make a real difference.

> QtAda's code includes both C/C++ and Ada code which refers to each
> others in both directions, so it is unpractical to separate it into
> two independent shared libraries to build C/C++ part using MSVC and
> Ada part using GNAT; but mixing of MSVC and GNAT object files in the
> same shared library is not supported now.

I agree. It is the Visual Studio's debugger, which makes MSVC attractive.
Since that won't work with GNAT, there seems to be no reason left to port
Qt into MSVC.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de