From jchris.fillionr at kitware.com Tue Sep 1 11:34:51 2015 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Tue, 1 Sep 2015 11:34:51 -0400 Subject: [Ctk-developers] CTK build error with Qt5 In-Reply-To: References: Message-ID: Hi Hongzhi, Julien pushed a fix few days ago that may be helpful to address that particular issue. See commit 8b12543 "Fix compilation on Visual Studio" on https://github.com/commontk/CTK/commits/master Let us know if that helps, Thanks Jc On Wed, Aug 26, 2015 at 10:05 PM, Hongzhi Lan wrote: > I also tried with Qt4.8.6 and the same issue happened. But If I tried CTK > code from April with Qt4.8.6, the build is good. I guess something changed > in CTK after then? > > > Thanks, > > Hongzhi > > > ------------------------------ > *From:* Ctk-developers on > behalf of Hongzhi Lan > *Sent:* Tuesday, August 25, 2015 6:32 PM > *To:* Jean-Christophe Fillion-Robin > *Cc:* ctk-developers at commontk.org > *Subject:* [Ctk-developers] CTK build error with Qt5 > > Hi Chris, > > I just tried today to build current CTK with Qt5, but failed. I used my > own VTK6.2.0, ITK4.5.1, PythonQt3.0 built with Qt5.4.1. The OS is Ubuntu > 14.04 64bit. The error is shown as below. I didn't have this error before. > > > Linking CXX shared library ../../../../bin/libCTKVisualizationVTKCore.so > CMakeFiles/CTKVisualizationVTKCore.dir/vtkLightBoxRendererManager.cpp.o: > In function `vtkRenderingCore_AutoInit::vtkRenderingCore_AutoInit()': > /home/hongzhi/ProgramFiles/VTK6.2.0-Qt5.4.1-Python2.7.6/Rendering/Core/vtkRenderingCoreModule.h:41: > undefined reference to `vtkRenderingFreeTypeOpenGL_AutoInit_Construct()' > CMakeFiles/CTKVisualizationVTKCore.dir/vtkLightBoxRendererManager.cpp.o: > In function `vtkRenderingCore_AutoInit::~vtkRenderingCore_AutoInit()': > /home/hongzhi/ProgramFiles/VTK6.2.0-Qt5.4.1-Python2.7.6/Rendering/Core/vtkRenderingCoreModule.h:41: > undefined reference to `vtkRenderingFreeTypeOpenGL_AutoInit_Destruct()' > collect2: error: ld returned 1 exit status > make[5]: *** [bin/libCTKVisualizationVTKCore.so.0.1.0] Error 1 > make[4]: *** > [Libs/Visualization/VTK/Core/CMakeFiles/CTKVisualizationVTKCore.dir/all] > Error 2 > make[3]: *** [all] Error 2 > make[2]: *** [CTK-prefix/src/CTK-stamp/CTK-build] Error 2 > make[1]: *** [CMakeFiles/CTK.dir/all] Error 2 > make: *** [all] Error 2 > > > Thanks! > Hongzhi > > > > On Wed, Apr 29, 2015 at 10:58 PM, Jean-Christophe Fillion-Robin < > jchris.fillionr at kitware.com> wrote: > >> Hi Hongzhi, >> >> Good to know you resolved the problem. >> >> On Wed, Apr 22, 2015 at 3:23 PM, Hongzhi Lan wrote: >> >>> ....../CTK-Qt5.4.1-Python2.7.6/CTK-build/Libs/Core/generated_cpp/org_commontk_CTKCore/org_commontk_CTKCore.h:9:19: >>> fatal error: QWidget: No such file or directory #include ^ >>> compilation terminated. >> >> >> It turns out that we already fixed that problem. The corresponding fixes >> has just been integrated into master. See [1] and [2] >> >> Let us know if you have any other issues. >> >> Thanks >> Jc >> >> [1] >> https://github.com/commontk/CTK/commit/e4e9cc326d4ab603785267defebcdcbf514d429d >> >> [2] https://github.com/commontk/CTK/pull/558#issuecomment-97669981 >> >> >> >> -- >> +1 919 869 8849 >> > > -- +1 919 869 8849 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Thu Sep 10 09:29:33 2015 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Thu, 10 Sep 2015 09:29:33 -0400 Subject: [Ctk-developers] Issue with plugin framework (was: Re: ctk bug report & questions) Message-ID: Hi Zoltan, NOTE: I added the developer list in cc Thanks for reaching out and welcome to the CTK community ! To report issue, we are using the Github issue tracker (this is the link "Report a problem" on the http://commontk.org page) See https://github.com/commontk/CTK/issues/new I also re-organized the "Getting started" page to be more clear. That should help answering your questions. http://commontk.org/index.php/Getting_Started To move forward, I would suggest you create an issue providing a simple example allowing to reproduce the problem. Looking at the changes associated with the CTK/Plugins folder, I couldn't spot an obvious change that would break things. See https://github.com/commontk/CTK/commits/master/Plugins That said, I am sure other folks on the list should be able to help you out. Let us know if you have any other questions, Thanks Jc On Wed, Sep 9, 2015 at 3:18 AM, wrote: > Dear Mr. Fillion-Robin, > > I write to you, because you seem to be the most active developer on CTK for > the last few months (according to the ctk-developers mailing list archive) > but this list is closed and I could not find any public lists that are used > for bug-reporting. > So I wonder what is the official way of doing this? Do I have to register > with github? > > Anyways: We're using CTK as a plugin manager in our university project and > we use the framework properties to pass some initial values to our plugins > (using > the launcher's setFrameworkProperties function). > > It has worked in the past but for some time now it seems to be broken, as > all keys set this way are lost at the time the plugins query those > properties.. > > Fixing it seems to be one-liner like: > > bool ctkPluginFrameworkLauncher::start(const QString& symbolicName, > ...... > if (context == 0 && d->fwFactory == 0) { > + d->fwProps = ctkPluginFrameworkProperties::getProperties(); > d->fwFactory.reset(new ctkPluginFrameworkFactory(d->fwProps)); > .... > > (well, actually there are other places like the install function where it > would also need > fixing..) > > Is this an intentional change in the library behaviour or could it be fixed > in the current version of the library? It it is intentional, is there an > equivalent mechanic to pass parameters to the start() function of the > plugins? > > Best regards, > Zoltan Bardosi > > PS: I've also tried to register to the ctk-developers list, but I'm not sure > if I would be authorized just like that.. :) > -- +1 919 869 8849 From jchris.fillionr at kitware.com Thu Sep 10 10:29:36 2015 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Thu, 10 Sep 2015 10:29:36 -0400 Subject: [Ctk-developers] Issue with plugin framework (was: Re: ctk bug report & questions) In-Reply-To: <20150910161750.29223rll7s2947pc@webmail.i-med.ac.at> References: <20150910161750.29223rll7s2947pc@webmail.i-med.ac.at> Message-ID: Hi Zoltan, You are welcome. [[ So that other can benefit from the conversation, I re-added the list in cc. Would be great if you could join the mailing list and include it in future reply :) ]] Since you already have a patch, may be you could create a pull request where you would just describe the issue. That would be a great first step. Later one, someone else may then be able to move forward if your patch and get it integrated. Thanks Jc On Thu, Sep 10, 2015 at 10:17 AM, wrote: > Dear Jean-Christophe, > > thank you for the answer. I will create a small example to trigger the > problem and put it up to the issue tracker, but it has a relatively low > priority in my todo list right now ;) > I'm quite sure that this can be easily patched, as I already did in my local > version, so patching it in the official version would be convenient, but it > is not that urgent. :) > > Best regards, > Zoltan Bardosi > > > > Quoting "Jean-Christophe Fillion-Robin" : > >> Hi Zoltan, >> >> NOTE: I added the developer list in cc >> >> Thanks for reaching out and welcome to the CTK community ! >> >> To report issue, we are using the Github issue tracker (this is the >> link "Report a problem" on the http://commontk.org page) >> >> See https://github.com/commontk/CTK/issues/new >> >> I also re-organized the "Getting started" page to be more clear. That >> should help answering your questions. >> >> http://commontk.org/index.php/Getting_Started >> >> To move forward, I would suggest you create an issue providing a >> simple example allowing to reproduce the problem. >> >> >> Looking at the changes associated with the CTK/Plugins folder, I >> couldn't spot an obvious change that would break things. >> See https://github.com/commontk/CTK/commits/master/Plugins >> >> >> That said, I am sure other folks on the list should be able to help you >> out. >> >> Let us know if you have any other questions, >> >> Thanks >> Jc >> >> On Wed, Sep 9, 2015 at 3:18 AM, >> wrote: >>> >>> Dear Mr. Fillion-Robin, >>> >>> I write to you, because you seem to be the most active developer on CTK >>> for >>> the last few months (according to the ctk-developers mailing list >>> archive) >>> but this list is closed and I could not find any public lists that are >>> used >>> for bug-reporting. >>> So I wonder what is the official way of doing this? Do I have to register >>> with github? >>> >>> Anyways: We're using CTK as a plugin manager in our university project >>> and >>> we use the framework properties to pass some initial values to our >>> plugins >>> (using >>> the launcher's setFrameworkProperties function). >>> >>> It has worked in the past but for some time now it seems to be broken, as >>> all keys set this way are lost at the time the plugins query those >>> properties.. >>> >>> Fixing it seems to be one-liner like: >>> >>> bool ctkPluginFrameworkLauncher::start(const QString& symbolicName, >>> ...... >>> if (context == 0 && d->fwFactory == 0) { >>> + d->fwProps = ctkPluginFrameworkProperties::getProperties(); >>> d->fwFactory.reset(new ctkPluginFrameworkFactory(d->fwProps)); >>> .... >>> >>> (well, actually there are other places like the install function where it >>> would also need >>> fixing..) >>> >>> Is this an intentional change in the library behaviour or could it be >>> fixed >>> in the current version of the library? It it is intentional, is there an >>> equivalent mechanic to pass parameters to the start() function of the >>> plugins? >>> >>> Best regards, >>> Zoltan Bardosi >>> >>> PS: I've also tried to register to the ctk-developers list, but I'm not >>> sure >>> if I would be authorized just like that.. :) >>> >> >> >> >> -- >> +1 919 869 8849 >> >> > > -- +1 919 869 8849