From haocheng.liu at kitware.com Tue Apr 4 10:11:10 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Tue, 4 Apr 2017 10:11:10 -0400 Subject: [Cmb-users] Ubuntu 16.04 + Quadro M2000M (maybe Linux) NVIDIA driver does not work with CMB ? Message-ID: Hi, Recently I upgrade my NIDIA driver to 370.28, ModelBuilder refuses to open the application with an error message as "core dumped"(Cannot initialize OpenGL window). After some trial and error, I found a work-around solution as: - Using* Nouveau display driver* from xserver-xory-video-nouveau for the video card - run application in cmd as: "*LIBGL_ALWAYS_SOFTWARE=1 ./your-path-to-application*". Without setting LIBGL_ALWAYS_SOFTWARE, you would get an error message as: intel-do-flush-locked-failed-input-output-error when trying to assign a color to model entity in ModelBuilder. It's said to be a bug with UXA and SNA acceleration. -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4421 <(518)%20881-4421> -------------- next part -------------- An HTML attachment was scrubbed... URL: From haocheng.liu at kitware.com Tue Apr 4 15:00:43 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Tue, 4 Apr 2017 15:00:43 -0400 Subject: [Cmb-users] Ubuntu 16.04 + Quadro M2000M (maybe Linux) NVIDIA driver does not work with CMB ? In-Reply-To: References: Message-ID: So here is the root cause: Recently CMB-superbuild is bumped to use ParaView 5.3.0. However, it is not happy with OpenGL drivers on Ubuntu 16.04. What you need to do is type in following commands if you want to build CMB-superbuild and run smoothly on Ubuntu16.04: ``` apt-add-repository ppa:oibaf/graphics-drivers apt-get update apt-get dist-upgrade ``` Reference link . On Tue, Apr 4, 2017 at 10:11 AM, Haocheng Liu wrote: > Hi, > > Recently I upgrade my NIDIA driver to 370.28, ModelBuilder refuses to open > the application with an error message as "core dumped"(Cannot initialize > OpenGL window). After some trial and error, I found a work-around solution > as: > > > - Using* Nouveau display driver* from xserver-xory-video-nouveau for > the video card > - run application in cmd as: "*LIBGL_ALWAYS_SOFTWARE=1 > ./your-path-to-application*". > > Without setting LIBGL_ALWAYS_SOFTWARE, you would get an error message as: > intel-do-flush-locked-failed-input-output-error > when > trying to assign a color to model entity in ModelBuilder. It's said to be a > bug with UXA and SNA acceleration. > > > -- > Best regards > Haocheng > > Haocheng LIU > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4421 <(518)%20881-4421> > -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4421 <(518)%20881-4421> -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Thu Apr 13 09:57:56 2017 From: david.thompson at kitware.com (David Thompson) Date: Thu, 13 Apr 2017 09:57:56 -0400 Subject: [Cmb-users] automoc symbol issues In-Reply-To: <58ef7483.2444810a.5844d.6cf3@mx.google.com> References: <58ef73ec.cb4e810a.18e38.03bd@mx.google.com> <58ef7483.2444810a.5844d.6cf3@mx.google.com> Message-ID: <9045ED30-3BD7-4A6B-887C-E28E4D3285AB@kitware.com> Hi TJ, In my version of CMB (admittedly not the latest master, but close), there is no EXPORT macro in the "class pqSMTKMeshInfo" declaration. David > On Apr 13, 2017, at 08:52, wrote: > > This got bounced from cmb-developers, so I am resending it here > > Sent from Mail for Windows 10 > > From: tj.corona at kitware.com > Sent: Thursday, April 13, 2017 7:49 AM > To: cmb-developers at kitware.com; Shawn Waldon > Subject: automoc symbol issues > > Hi all, > > I am trying to fix a bug I introduced into the windows build of ModelBuilder, and am having little luck. It looks like the auto-MOC?d file generated for my class has bad dll linkage. This is the perfect storm of Windows, Qt and linking for me, and I am completely out of my depth. Does anyone have any idea why my class (which looks exactly like the other Qt-derived classes in this directory) won?t compile on Windows? Here?s a snipped of the errors I?m getting: > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\applications\modelbuilder\ModelBuilder_automoc.dir/moc_pqSMTKMeshInfo_OPAOOSEHZX24R7.cpp(52): warning C4273: 'staticMetaObject': inconsistent dll linkage > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\applications\modelbuilder\modelbuilder_automoc.dir\../../../../../src/Source/Applications/ModelBuilder/pqSMTKMeshInfo.h(38): note: see previous definition of 'public: static QMetaObject const pqSMTKMeshInfo::staticMetaObject' > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\applications\modelbuilder\ModelBuilder_automoc.dir/moc_pqSMTKMeshInfo_OPAOOSEHZX24R7.cpp(52): error C2491: 'pqSMTKMeshInfo::staticMetaObject': definition of dllimport static data member not allowed > > Thanks! > > Sincerely, > T.J. > > Sent from Mail for Windows 10 From haocheng.liu at kitware.com Thu Apr 13 10:39:42 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Thu, 13 Apr 2017 10:39:42 -0400 Subject: [Cmb-users] automoc symbol issues In-Reply-To: <9045ED30-3BD7-4A6B-887C-E28E4D3285AB@kitware.com> References: <58ef73ec.cb4e810a.18e38.03bd@mx.google.com> <58ef7483.2444810a.5844d.6cf3@mx.google.com> <9045ED30-3BD7-4A6B-887C-E28E4D3285AB@kitware.com> Message-ID: Hi TJ, I did some simple tests on Kerbin(windows10 + VS2015). By simply removing **#include "pqComponentsModule.h"** and **PQCOMPONENTS_EXPORT** in pqSMTKInfoPanel.h, the build succeeds. It seems that PQCOMPONENTS_EXPORT is used in ParView to export model pqComponents symbol, may I ask why we need it in CMB? On Thu, Apr 13, 2017 at 9:57 AM, David Thompson wrote: > Hi TJ, > > In my version of CMB (admittedly not the latest master, but close), there > is no EXPORT macro in the "class pqSMTKMeshInfo" declaration. > > David > > > On Apr 13, 2017, at 08:52, < > tj.corona at kitware.com> wrote: > > > > This got bounced from cmb-developers, so I am resending it here > > > > Sent from Mail for Windows 10 > > > > From: tj.corona at kitware.com > > Sent: Thursday, April 13, 2017 7:49 AM > > To: cmb-developers at kitware.com; Shawn Waldon > > Subject: automoc symbol issues > > > > Hi all, > > > > I am trying to fix a bug I introduced into the windows build of > ModelBuilder, and am having little luck. It looks like the auto-MOC?d file > generated for my class has bad dll linkage. This is the perfect storm of > Windows, Qt and linking for me, and I am completely out of my depth. Does > anyone have any idea why my class (which looks exactly like the other > Qt-derived classes in this directory) won?t compile on Windows? Here?s a > snipped of the errors I?m getting: > > > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\ > applications\modelbuilder\ModelBuilder_automoc.dir/moc_ > pqSMTKMeshInfo_OPAOOSEHZX24R7.cpp(52): warning C4273: 'staticMetaObject': > inconsistent dll linkage > > > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\ > applications\modelbuilder\modelbuilder_automoc.dir\../.. > /../../../src/Source/Applications/ModelBuilder/pqSMTKMeshInfo.h(38): > note: see previous definition of 'public: static QMetaObject const > pqSMTKMeshInfo::staticMetaObject' > > > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\ > applications\modelbuilder\ModelBuilder_automoc.dir/moc_ > pqSMTKMeshInfo_OPAOOSEHZX24R7.cpp(52): error C2491: 'pqSMTKMeshInfo::staticMetaObject': > definition of dllimport static data member not allowed > > > > Thanks! > > > > Sincerely, > > T.J. > > > > Sent from Mail for Windows 10 > > -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4421 <(518)%20881-4421> -------------- next part -------------- An HTML attachment was scrubbed... URL: From tj.corona at kitware.com Thu Apr 13 10:42:32 2017 From: tj.corona at kitware.com (tj.corona at kitware.com) Date: Thu, 13 Apr 2017 09:42:32 -0500 Subject: [Cmb-users] automoc symbol issues In-Reply-To: References: <58ef73ec.cb4e810a.18e38.03bd@mx.google.com> <58ef7483.2444810a.5844d.6cf3@mx.google.com> <9045ED30-3BD7-4A6B-887C-E28E4D3285AB@kitware.com> Message-ID: <58ef8e58.c5fa0d0a.ad1d7.0bd4@mx.google.com> Thanks Haocheng and David! You guys solved my problem. The MR is here if anyone wants to review: https://gitlab.kitware.com/cmb/cmb/merge_requests/358 Sent from Mail for Windows 10 From: Haocheng Liu Sent: Thursday, April 13, 2017 9:40 AM To: David Thompson Cc: TJ Corona; Robert Michael O'Bara; Ben Boeckel; John Tourtellott; cmb-users Subject: Re: automoc symbol issues Hi TJ, I ?did some simple tests on Kerbin(windows10 + VS2015). By simply removing **#include "pqComponentsModule.h"** and **PQCOMPONENTS_EXPORT** in pqSMTKInfoPanel.h, the build succeeds. It seems that?PQCOMPONENTS_EXPORT is used in ParView to export model pqComponents symbol, may I ask why we need it in CMB?? On Thu, Apr 13, 2017 at 9:57 AM, David Thompson wrote: Hi TJ, In my version of CMB (admittedly not the latest master, but close), there is no EXPORT macro in the "class pqSMTKMeshInfo" declaration. ? ? ? ? David > On Apr 13, 2017, at 08:52, wrote: > > This got bounced from cmb-developers, so I am resending it here > > Sent from Mail for Windows 10 > > From: tj.corona at kitware.com > Sent: Thursday, April 13, 2017 7:49 AM > To: cmb-developers at kitware.com; Shawn Waldon > Subject: automoc symbol issues > > Hi all, > > I am trying to fix a bug I introduced into the windows build of ModelBuilder, and am having little luck. It looks like the auto-MOC?d file generated for my class has bad dll linkage. This is the perfect storm of Windows, Qt and linking for me, and I am completely out of my depth. Does anyone have any idea why my class (which looks exactly like the other Qt-derived classes in this directory) won?t compile on Windows? Here?s a snipped of the errors I?m getting: > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\applications\modelbuilder\ModelBuilder_automoc.dir/moc_pqSMTKMeshInfo_OPAOOSEHZX24R7.cpp(52): warning C4273: 'staticMetaObject': inconsistent dll linkage > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\applications\modelbuilder\modelbuilder_automoc.dir\../../../../../src/Source/Applications/ModelBuilder/pqSMTKMeshInfo.h(38): note: see previous definition of 'public: static QMetaObject const pqSMTKMeshInfo::staticMetaObject' > > c:\dev\cmb_sb_vs2015\superbuild\cmb\build\source\applications\modelbuilder\ModelBuilder_automoc.dir/moc_pqSMTKMeshInfo_OPAOOSEHZX24R7.cpp(52): error C2491: 'pqSMTKMeshInfo::staticMetaObject': definition of dllimport static data member not allowed > > Thanks! > > Sincerely, > T.J. > > Sent from Mail for Windows 10 -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone:?518-881-4421 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Tue Apr 18 15:21:54 2017 From: david.thompson at kitware.com (David Thompson) Date: Tue, 18 Apr 2017 15:21:54 -0400 Subject: [Cmb-users] Classes in CMB Message-ID: Hi all, After the discussion of the bug Alvaro is running into, I sketched this up based on a post-it note drawing I made to help me understand how CMB is organized. There are plenty of objects not shown, but what's shown should be useful. David -------------- next part -------------- A non-text attachment was scrubbed... Name: cmb-classes.pdf Type: application/pdf Size: 13077 bytes Desc: not available URL: From ben.boeckel at kitware.com Thu Apr 20 11:59:27 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 20 Apr 2017 11:59:27 -0400 Subject: [Cmb-users] Qt5 test results Message-ID: <20170420155927.GA18601@megas.kitware.com> Hi, Here's a dashboard submission for a CMB built with Qt5. Note that it's on my setup which tends to make some oddball failures that won't show up anywhere else (like off-by-one image sizes), but it's better than 50% passing :) ). Lots of warnings from Qt about signals and slots not existing anymore. https://open.cdash.org/buildSummary.php?buildid=4862413 --Ben From david.thompson at kitware.com Fri Apr 28 16:39:46 2017 From: david.thompson at kitware.com (David Thompson) Date: Fri, 28 Apr 2017 16:39:46 -0400 Subject: [Cmb-users] Attribute system change Message-ID: <6BF0FD2B-85C6-429E-80BF-D7B9FF50FF34@kitware.com> Hi all, I've submitted merge requests for SMTK[1] and CMB[2] that convert SMTK's API to use shared pointers for attribute system instances. This is needed in order for the model manager to properly update associations with attributes when model entities are split or merged by modeling operations. What this means for you is that you can no longer create attribute systems like so: smtk::attribute::System someSystem; // C++ someSystem = smtk.attribute.System() # Python Instead, you should: auto someSystem = smtk::attribute::System::create(); // C++, returns a SystemPtr someSystem = smtk.attribute.System.create() # Python Note that this makes creating an attribute system the same as creating a model manager (which already has a static "create" method). David [1]: https://gitlab.kitware.com/cmb/smtk/merge_requests/567 [2]: https://gitlab.kitware.com/cmb/cmb/merge_requests/378