From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,9192417d428824a0
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!v25g2000yqk.googlegroups.com!not-for-mail
From: Alexis <jose_alexis_paez_thurgood@hotmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Problem with QTAda 3.0 and QTCore4.dll on Windows
Date: Thu, 7 Jan 2010 13:39:40 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <800b2914-d8c9-4c72-bf04-ccf53f091ae9@v25g2000yqk.googlegroups.com>
References: 
 <1660bebd-45ca-4568-b92a-380614d94ecc@c34g2000yqn.googlegroups.com>
	<8ec14209-e505-4873-86b4-294149841777@v25g2000yqk.googlegroups.com>
	<bddbcb0d-d573-4152-899f-d7a700f439f6@m16g2000yqc.googlegroups.com>
	<KWf1n.4151$%54.3403@newsfe22.ams2>
 <199i04cdgiqlc$.1tlj9wnffh6g9$.dlg@40tude.net>
NNTP-Posting-Host: 62.87.117.243
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1262900380 23257 127.0.0.1 (7 Jan 2010 21:39:40
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 7 Jan 2010 21:39:40 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: v25g2000yqk.googlegroups.com; posting-host=62.87.117.243;
	posting-account=fqT3AgoAAACuynC33fo8vJMqk6Lnw_it
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
	AppleWebKit/532.0 (KHTML,
 like Gecko) Chrome/3.0.195.38 Safari/532.0,gzip(gfe),gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:8658
Date: 2010-01-07T13:39:40-08:00
List-Id: <comp.lang.ada>

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.