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

[Vadim Godunko <vgodunko@gmail.com>]

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.

> > Then you will end up with two runtimes for C++, and to run MSVC and
> > GCC(g++) in parallel requires a very consistent way of doing things
> > since among all other things ther will be two different heaps...
>
> Actually I used such combinations in other cases (not Qt), e.g. GNAT Ada
> run-time + MSVC (sometimes with MFT!) + some bunch of third party libraries
> of unknown language and origin.
>
> The key issue is to set proper compiler/linker options for the MSVC
> project. Which is FAR from being trivial. Another huge issue is deployment,
> with MS manifests (due to broken implementations of) you simply cannot tell
> if linked code will or will not work on another computer.
>
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.