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

[Alexis <jose_alexis_paez_thurgood@hotmail.com>]

On 7 ene, 11:59, "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.
>
> > 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.
>
> --
> Regards,
> Dmitry A. Kazakovhttp://www.dmitry-kazakov.de

Thanks a lot to all of you, your advice has been very helpful. I have
now installed QT 4.5.1 MinGW on my machine and the QtAda programs work
fine, which is what I wanted.

I don't remember seeing any mention of this fact on the QtAda website,
it might be something interesting to add a note on this.

May thanks!
Best regards, Alexis.