- From: alan.garny at dpag.ox.ac.uk (Alan Garny)
- Subject: [cellml-dev] Using the CellML API with Qt Creator (solved) was Re: CellML 1.10rc2
- Date: Tue, 20 Sep 2011 19:22:37 +1200
To add to what Andrew has just said, I can now not only confirm that the
CellML binaries work fine for me using my Qt/C++ environment and this on
Windows (32-bit; with the standard libstdc++-6.dll), Linux (both 32-bit and
64-bit) and Mac OS X (64-bit in my case), but I am now able to use the
CellML binaries from within OpenCOR and this on all the aforementioned
platforms. Nice! If anything, I just wish I didn't have to distribute yet
another library (libstdc++-6.dll) on Windows, but since a deployed Qt
application doesn't indeed require that DLL, we should be fine... that is,
as long no other library ever needs the Qt patched libstdc++-6.dll...
Alan
>
-----Original Message-----
>
From: cellml-tools-developers-bounces at cellml.org [mailto:cellml-tools-
>
developers-bounces at cellml.org] On Behalf Of Andrew Miller
>
Sent: 20 September 2011 16:19
>
To: cellml-tools-developers at cellml.org
>
Subject: Re: [cellml-dev] Using the CellML API with Qt Creator (solved)
was
>
Re: CellML 1.10rc2
>
>
Hi all,
>
>
Just to update you all on the Qt Creator situation:
>
1. With libstdc++-6.dll from standard MinGW, Alan has now been able to
>
build a working test program using the CellML API and Qt Creator.
>
2. By default, Qt Creator builds Windows subsystem binaries, so it is
>
impossible to see the output from the example application, hence why it
>
looks like it isn't working.
>
3. I have grepped the output from objdump -p over every DLL and EXE in
>
my Qt SDK install, and got no hits at all (except for libstdc++-6.dll
itself, of
>
course), meaning that libstdc++-6.dll is not needed by any of the Qt
libraries,
>
and it is perfectly safe to use the version from the official MinGW
builds.
>
>
It therefore looks like Alan has successfully reached the point where he
can
>
create apps using the CellML API in Qt Creator on Windows, Linux, and Mac
>
OS X.
>
>
Best wishes,
>
Andrew
>
>
On 15/09/11 19:28, Alan Garny wrote:
>
> Hi Andrew,
>
>
>
>>> It seems to me that you are overcomplicating things. The whole idea
>
>>> of the Qt SDK is that you have *everything* you need to build a Qt
>
>>> application. On Windows, this includes a patched version of MinGW
>
>>> which does come with a
>
>>> make:
>
>>
>
>> Okay, found it, I was looking for make.exe not mingw32-make.exe; I
>
>> guess you are setting an environment variable or CMake variable to
>
>> tell it to
>
> use
>
>> mingw32-make?
>
>
>
> No, I just use CMake's -G option:
>
> https://github.com/opencor/opencor/blob/master/makeproj.bat.
>
> Otherwise, in my PATH, I have added the paths to CMake, MinGW and Qt
>
> (see http://www.opencor.ws/developer/preRequirements.html).
>
>
>
>> However, the point of the Cygwin bash script (or you could use a bat
>
>> file) is to isolate the problem by giving greater control over
>
>> exactly
>
> what is
>
>> run and what environment variables are set - so it is still worth
doing.
>
>
>
> My personal point is that I don't use Cygwin, so unless I am
>
> completely mistaken what you are suggesting shouldn't apply to me.
>
> Anyway, you are over your allocated CellML time for this week, so
>
> let's have a look at it next week.
>
>
>
> Alan
>
>
>
> _______________________________________________
>
> cellml-tools-developers mailing list
>
> cellml-tools-developers at cellml.org
>
> http://lists.cellml.org/mailman/listinfo/cellml-tools-developers
>
>
_______________________________________________
>
cellml-tools-developers mailing list
>
cellml-tools-developers at cellml.org
>
http://lists.cellml.org/mailman/listinfo/cellml-tools-developers
Archive powered by MHonArc 2.6.18.