[Paraview-developers] Paraview and VS2013 compile errors
Lodron, Gerald
Gerald.Lodron at joanneum.at
Thu Sep 4 16:13:18 EDT 2014
Hi,
Thanks for clearification (could not find details about that stuff). Since we have our own build system I need to migrate Paraview and VTK to it, so I am afraid that I cannot use the superbuild, I need to link to our own compiled python/qt/boost...Since I/my small group are the only ones which use vtk I could also use the internal VTK of PV but it would be really great if paraview would get working with qt5 (since our internal's are not compatible with qt4 anymore and I/we work on an extremely old qt4 branch).
Is there any timeline to support qt5 or the external VTK? Is PV generally not supporting VS2013 or only superbuild (which wouldn't be a problem)? The problem is that we cannot work with VS2008 any more since many other toolkits (especially PCL) use C++11 features (and our company IT only has VS2008 and 2013).
Oh sometimes live is really hard....
Best regards,
Gerald
-----Ursprüngliche Nachricht-----
Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Gesendet: Donnerstag, 04. September 2014 20:56
An: Lodron, Gerald
Cc: Frank TT; Paraview Developer (Paraview-developers at paraview.org)
Betreff: Re: [Paraview-developers] Paraview and VS2013 compile errors
Gerald,
You should brace yourself :):
+ Qt 5 support in ParaView currently is experimental. We still aren't
officially supporting it.
+ VS2013 suppport for Superbuilds is experimental too. Should work,
but not if you're using internal Python yet.
+ External VTK is definitely not supported yet, I am afraid.
Utkarsh
On Thu, Sep 4, 2014 at 2:04 PM, Lodron, Gerald <Gerald.Lodron at joanneum.at> wrote:
> Hi
>
> Omg, there is a Qt4 you are right. Should be fixed in root cmake! Any ideas of the max_alight_t issue?
>
> No, our "institute" toolkit is also switched to qt5 so it would be adviceable that I also switch my paraview/vtk stuff to same version. And I am also migrating from VS 2008 to 2013 at the same time, so many things to do. I also found out that I need to build qt with the no-angle and opengl switch to get the vtk opengl stuff working...., omg, everything back to beginning....
>
> Does the knob of "ExternalVTK" work? In PV 4.1 this didn't work... Perhaps I will see it in 2-3 days when I rebuild qt, this would be really great ...
>
> Thanks for hint and best regards,
> Gerald
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Paraview-developers
> [mailto:paraview-developers-bounces at paraview.org] Im Auftrag von Frank
> TT
> Gesendet: Donnerstag, 04. September 2014 19:34
> An: paraview-developers at paraview.org
> Betreff: Re: [Paraview-developers] Paraview and VS2013 compile errors
>
> On Thu, 2014-09-04 at 13:23 +0000, Lodron, Gerald wrote:
>> Hi
>>
>> I am compiling PV with qt 5.2.1, internal VTK and boost 1.55 (for ReebGraph), under 64bit (without python) and get following errors:
>>
>> Min max unknown in protobuf, following patch works:
>> https://code.google.com/p/protobuf/issues/detail?id=531
>>
>> I also get many
>> 2>C:\Program Files (x86)\Microsoft Visual Studio
>> 2>12.0\VC\include\type_traits(1220): error C2065: 'max_align_t' :
>> 2>undeclared identifier
>>
>> Adding #include <stddef.h> to common.h of protobuf solved that in porotobuf but I get it also in CommandLineArguments.cxx of vtksys where that solution does not worked...
>>
>> Additionally I get many linker errors:
>> 6>QtTesting_automoc.obj : error LNK2005: "public: static struct
>> 6>QMetaObject const pqComboBoxEventTranslator::staticMetaObject"
>> 6>(?staticMetaObject at pqComboBoxEventTranslator@@2UQMetaObject@@B)
>> 6>already defined in moc_pqComboBoxEventTranslator.obj
>> 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual
>> 9>struct QMetaObject const * __cdecl
>> 9>QVTKPlugin::metaObject(void)const "
>> 9>(?metaObject at QVTKPlugin@@UEBAPEBUQMetaObject@@XZ) already defined
>> 9>in moc_Q4VTKWidgetPlugin.obj
>> 6>QtTesting_automoc.obj : error LNK2005: "private: static void
>> 6>__cdecl pqComboBoxEventTranslator::qt_static_metacall(class QObject
>> 6>*,enum QMetaObject::Call,int,void * *)"
>> 6>(?qt_static_metacall at pqComboBoxEventTranslator@@CAXPEAVQObject@@W4C
>> 6>a
>> 6>ll at QMetaObject@@HPEAPEAX at Z) already defined in
>> 6>moc_pqComboBoxEventTranslator.obj
>> 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual void
>> 9>* __cdecl QVTKPlugin::qt_metacast(char const *)"
>> 9>(?qt_metacast at QVTKPlugin@@UEAAPEAXPEBD at Z) already defined in
>> 9>moc_Q4VTKWidgetPlugin.obj QVTKWidgetPlugin_automoc.obj : error
>> 9>LNK2005: "public: virtual int __cdecl QVTKPlugin::qt_metacall(enum
>> 9>QMetaObject::Call,int,void * *)"
>> 9>(?qt_metacall at QVTKPlugin@@UEAAHW4Call at QMetaObject@@HPEAPEAX at Z)
>> 9>already defined in moc_Q4VTKWidgetPlugin.obj
>> 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "private: static void
>> 9>__cdecl QVTKPlugin::qt_static_metacall(class QObject *,enum
>> 9>QMetaObject::Call,int,void * *)"
>> 9>(?qt_static_metacall at QVTKPlugin@@CAXPEAVQObject@@W4Call at QMetaObject
>> 9>@
>> 9>@HPEAPEAX at Z) already defined in moc_Q4VTKWidgetPlugin.obj
>> 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual
>> 9>struct QMetaObject const * __cdecl
>> 9>QVTKWidget::metaObject(void)const "
>> 9>(?metaObject at QVTKWidget@@UEBAPEBUQMetaObject@@XZ) already defined
>> 9>in moc_Q4VTKWidgetPlugin.obj QVTKWidgetPlugin_automoc.obj : error
>> 9>LNK2005: "public: virtual void * __cdecl
>> 9>QVTKWidget::qt_metacast(char const *)"
>> 9>(?qt_metacast at QVTKWidget@@UEAAPEAXPEBD at Z) already defined in
>> 9>moc_Q4VTKWidgetPlugin.obj QVTKWidgetPlugin_automoc.obj : error
>> 9>LNK2005: "public: virtual int __cdecl QVTKWidget::qt_metacall(enum
>> 9>QMetaObject::Call,int,void * *)"
>> 9>(?qt_metacall at QVTKWidget@@UEAAHW4Call at QMetaObject@@HPEAPEAX at Z)
>> 9>already defined in moc_Q4VTKWidgetPlugin.obj
>> 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "private: static void
>> 9>__cdecl QVTKWidget::qt_static_metacall(class QObject *,enum
>> 9>QMetaObject::Call,int,void * *)"
>> 9>(?qt_static_metacall at QVTKWidget@@CAXPEAVQObject@@W4Call at QMetaObject
>> 9>@
>> 9>@HPEAPEAX at Z) already defined in moc_Q4VTKWidgetPlugin.obj
>> 9>QVTKWidgetPlugin_automoc.obj : error LNK2005:
>> 9>qt_plugin_query_metadata already defined in
>> 9>moc_Q4VTKWidgetPlugin.obj QVTKWidgetPlugin_automoc.obj : error
>> 9>LNK2005: qt_plugin_instance already defined in
>> 9>moc_Q4VTKWidgetPlugin.obj
>>
>
> On my first build I've got similar errors.
>
> You see in the last pasted line "… moc_Q4VTKWidgetPlugin.obj" a hint. I used Qt 4.8.6 and it builds. If you have a look in the CMakeLists.txt there will it be more clear. For PV 4.1.0 you will find this in line 409 ff.
> Maybe you try Qt 4.8.* to build PV.
>
> Greetings
> Frank
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
More information about the Paraview-developers
mailing list