On Wed, Jan 4, 2012 at 2:47 PM, Denis Dzyubenko wrote:
> On Tue, Jan 3, 2012 at 7:16 PM, wrote:
>> On 03/01/2012 12:01, ext Thiago Macieira wrote:
>>> On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
That's the thing - it doesn't work in some cases - if you do
in-sourc
Hi,
On Tue, Jan 3, 2012 at 7:16 PM, wrote:
> On 03/01/2012 12:01, ext Thiago Macieira wrote:
>> On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
>>> That's the thing - it doesn't work in some cases - if you do
>>> in-source-tree build of the attached project. Well now thinking
>
On Tuesday, 3 de January de 2012 18.29.11, marius.storm-ol...@nokia.com wrote:
> > I solved the problem by using a special compiler, which was already
> > present in src/gui/gui.pro. qmake doesn't look into SSE2_SOURCES,
> > AVX_SOURCES, NEON_SOURCES.
>
> Right, that would work too. (as would a sep
On 03/01/2012 12:20, ext Thiago Macieira wrote:
> On Tuesday, 3 de January de 2012 18.16.46,
> marius.storm-ol...@nokia.com wrote:
>>> I know that because I had the exactly opposite problem Friday: I
>>> had one .cpp (qdrawhelper.cpp) that I wanted to be compiled on
>>> its own *and* as an #include
On Tuesday, 3 de January de 2012 18.16.46, marius.storm-ol...@nokia.com wrote:
> > I know that because I had the exactly opposite problem Friday: I had
> > one .cpp (qdrawhelper.cpp) that I wanted to be compiled on its own
> > *and* as an #include from somewhere else. qmake wouldn't do it.
>
> You
On 03/01/2012 12:01, ext Thiago Macieira wrote:
> On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
>> That's the thing - it doesn't work in some cases - if you do
>> in-source-tree build of the attached project. Well now thinking
>> about it, it is probably a bug in qmake.
Sounds
On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
> That's the thing - it doesn't work in some cases - if you do
> in-source-tree build of the attached project. Well now thinking about
> it, it is probably a bug in qmake.
>
> Denis.
You said:
> This is because qmake decided that m
Hi Thiago,
2012/1/3 Thiago Macieira :
> On Friday, 30 de December de 2011 14.55.55, Denis Dzyubenko wrote:
>> In qt5 modules we have exactly the same problem as in namespaced-Qt
>> itself. Hence my suggestion to solve it in the same way - I would like
>> to be able to re-use that QT_BEGIN_MOC_NAME
On Friday, 30 de December de 2011 14.55.55, Denis Dzyubenko wrote:
> In qt5 modules we have exactly the same problem as in namespaced-Qt
> itself. Hence my suggestion to solve it in the same way - I would like
> to be able to re-use that QT_BEGIN_MOC_NAMESPACE for qt5 modules, to
> be able to redef
On Friday 30 December 2011 14:55:55 Denis Dzyubenko wrote:
> Hi guys,
>
> With a qt5 module that we are developing, qtjsondb, we stumbled upon
> an issue with moc and our classes that are inside a namespace. Let me
> illustrate it with a code:
>
> jsondb-global.h:
>
> #if defined(QT_NAMESPACE)
>
Hi guys,
With a qt5 module that we are developing, qtjsondb, we stumbled upon
an issue with moc and our classes that are inside a namespace. Let me
illustrate it with a code:
jsondb-global.h:
#if defined(QT_NAMESPACE)
# define QT_ADDON_JSONDB_BEGIN_NAMESPACE namespace QT_NAMESPACE {
namespace Q
11 matches
Mail list logo
