19 июня 2014 г., в 10:36, Koehne Kai написал(а):
>
>
>> -Original Message-
>> From: interest-bounces+kai.koehne=digia@qt-project.org
>> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
>> Of K. Frank
>> Sent: Wednesday, June 18, 2014 9:04 PM
>> To: Qt-interes
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
> Of K. Frank
> Sent: Wednesday, June 18, 2014 9:04 PM
> To: Qt-interest
> Subject: Re: [Interest] Is a pre-built mingw-w64 Qt availa
Hi Kai and Harish!
On Wed, Jun 18, 2014 at 11:18 AM, Harish Surana wrote:
> He is looking for 64 bit mingw builds not 32 bit :)
Yes, that is correct. I am hoping to find a 64-bit mingw-w64 build.
> On Wed, Jun 18, 2014 at 5:06 PM, Koehne Kai wrote:
>> > -Original Message-
>> > [mailto
>
> Then the plugin will derive from one of the DerivedX classes, and provide
> a method in the interface which will list its implemented derived class
> names as strings, and provide a factory for them returning Base* objects.
>
> Then, the app will dynamic_cast these pointers to DerivedA, Derived
Den 18-06-2014 17:31, Etienne Sandré-Chardonnal skrev:
> Which defeats the purpose of the plugin, which should define a subclass
> of a base class common between plugins (and app).
> Can I define the base class in a separate library, dynamically linked
> with every plugin & the app?
Yes, that's ex
Which defeats the purpose of the plugin, which should define a subclass of
a base class common between plugins (and app).
Can I define the base class in a separate library, dynamically linked with
every plugin & the app?
Etienne
> Will the dynamic_cast work? Is there a special way to export/dec
He is looking for 64 bit mingw builds not 32 bit :)
On Wed, Jun 18, 2014 at 5:06 PM, Koehne Kai wrote:
>
>
> > -Original Message-
> > From: interest-bounces+kai.koehne=digia@qt-project.org
> > [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
> > Of K. Frank
>
Em qua 18 jun 2014, às 15:32:51, Bo Thorsen escreveu:
> You can use a static library, but then stuff like singletons won't work
> reliably.
You can't use a static library for RTTI.
In order to get the RTTI to work, the class's typeinfo needs to be in a single
place. On Windows, due to the DLL l
Em qua 18 jun 2014, às 15:20:03, Etienne Sandré-Chardonnal escreveu:
> Hi,
>
> I would like to implement a plugin system in my app and I'm totally
> ignorant of dynamic library mechanisms. So I'm trying with a QPlugin. I'm
> using Qt 4.8.5, gcc 4.8.0 mingw64.
>
> The question is : can RTTI work b
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
> Of K. Frank
> Sent: Wednesday, June 18, 2014 2:49 PM
> To: Qt-interest
> Subject: [Interest] Is a pre-built mingw-w64 Qt available?
Den 18-06-2014 16:04, Roland Winklmeier skrev:
> unix:QMAKE_POST_LINK += cp $$DESTDIR/$$TARGET.so $$DESTDIR/$$TARGET.xpl
>
> Written from memory, you probably need to fix it a bit.
>
> I hope this helps,
>
>
> Thanks Bo. You pointed me into the right direction.
You're very welcome :)
>
> unix:QMAKE_POST_LINK += cp $$DESTDIR/$$TARGET.so $$DESTDIR/$$TARGET.xpl
>
> Written from memory, you probably need to fix it a bit.
>
> I hope this helps,
>
Thanks Bo. You pointed me into the right direction.
CONFIG += plugin
unix:QMAKE_POST_LINK += mv $$DESTDIR/lib$${TARGET}.so
$${DESTDIR}/$
Den 18-06-2014 15:20, Etienne Sandré-Chardonnal skrev:
> Hi,
>
> I would like to implement a plugin system in my app and I'm totally
> ignorant of dynamic library mechanisms. So I'm trying with a QPlugin.
> I'm using Qt 4.8.5, gcc 4.8.0 mingw64.
>
> The question is : can RTTI work between the plugi
Den 18-06-2014 13:23, Roland Winklmeier skrev:
> Hey there,
>
> I have a project which builds a plugin for a cross platform application.
> This application expects its plugins to have the extension *.xpl. After
> reading the docs and setting the qmake variables to
>
> TARGET = plugin
> TARGET_EXT=x
Hello Yves!
Thank you.
On Wed, Jun 18, 2014 at 9:17 AM, Yves Bailly
wrote:
> On 18/06/2014 14:49, K. Frank wrote:
>> Hello List!
>>
>> Is Qt (preferably the latest version) available pre-built with
>> mingw-w64? I would hope for at least gcc 4.8, but preferably
>> gcc 4.9.
>
> http://tver-soft.
Hi,
I would like to implement a plugin system in my app and I'm totally
ignorant of dynamic library mechanisms. So I'm trying with a QPlugin. I'm
using Qt 4.8.5, gcc 4.8.0 mingw64.
The question is : can RTTI work between the plugin and the app?
I will define and include these headers in both the
On 18/06/2014 14:49, K. Frank wrote:
> Hello List!
>
> Is Qt (preferably the latest version) available pre-built with
> mingw-w64? I would hope for at least gcc 4.8, but preferably
> gcc 4.9.
http://tver-soft.org/qt64
scroll down for MinGW builds. No 4.9 for now it seems though.
Regards,
--
Hi Harish!
Thank you.
On Wed, Jun 18, 2014 at 9:09 AM, Harish Surana wrote:
> http://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds/
Somehow I had overlooked that on the mingwbuilds web site.
Thanks for pointing me in the right direction.
K. Frank
> On Wed, Ju
http://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds/
On Wed, Jun 18, 2014 at 2:49 PM, K. Frank wrote:
> Hello List!
>
> Is Qt (preferably the latest version) available pre-built with
> mingw-w64? I would hope for at least gcc 4.8, but preferably
> gcc 4.9.
>
>
Hello List!
Is Qt (preferably the latest version) available pre-built with
mingw-w64? I would hope for at least gcc 4.8, but preferably
gcc 4.9.
I've looked at both the qt-project and mingw-w64 web sites,
but nothing has jumped out at me.
Thanks.
K. Frank
Hey there,
I have a project which builds a plugin for a cross platform application.
This application expects its plugins to have the extension *.xpl. After
reading the docs and setting the qmake variables to
TARGET = plugin
TARGET_EXT=xpl
I expected to get a shared library called "plugin.xpl". O
21 matches
Mail list logo
