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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no 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
Path: 
 g2news1.google.com!postnews.google.com!j5g2000yqm.googlegroups.com!not-for-mail
From: Vadim Godunko <vgodunko@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Problem with QTAda 3.0 and QTCore4.dll on Windows
Date: Thu, 7 Jan 2010 14:11:37 -0800 (PST)
Organization: http://groups.google.com
Message-ID: <ec2d7604-ed68-441e-96f5-5fc946184ad5@j5g2000yqm.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: 87.117.37.223
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1262902297 12146 127.0.0.1 (7 Jan 2010 22:11:37
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 7 Jan 2010 22:11:37 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: j5g2000yqm.googlegroups.com; posting-host=87.117.37.223;
	posting-account=niG3UgoAAAD7iQ3takWjEn_gw6D9X3ww
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6)
	Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6,gzip(gfe),gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:8659
Date: 2010-01-07T14:11:37-08:00
List-Id: <comp.lang.ada>

On Jan 7, 1:59=A0pm, "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 gue=
ss
> 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 librari=
es
> 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 deploymen=
t,
> with MS manifests (due to broken implementations of) you simply cannot te=
ll
> 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.