[slicer-devel] error instantiating python modules in Slicer4

Jean-Christophe Fillion-Robin jchris.fillionr at kitware.com
Sat Mar 24 19:56:41 EDT 2012


Hi Daniel,

Considering VTK 5.10 is now used to build Slicer, doing a clean build is
the safest option.

In the mean time, I would also recommend you to build against Qt 4.7.4.
See
http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.0/Developers/Build_Instructions/Prerequisites/Build_Instructions_for_QT

This is now the new Qt minimum required version on all platform. See
https://github.com/Slicer/Slicer/commit/898bb14efdd912023de8e787c4267124a5cc49f0

Note also that if people feel like building against an older version of Qt,
this is still possible  by configuring the option
Slicer_REQUIRED_QT_VERSION.

Hth
Jc

On Sat, Mar 24, 2012 at 11:29 AM, <danieljohnsonusa at netscape.net> wrote:

> I did the svn co command this morning to check out revision 19695, and I
> got the same errors as before.  I noticed that the first error was that
> there was no module named qSlicerAnnotationsModuleWidgets.  I went to open
> up the qSlicerAnnotationsModuleWidgets.sln and build it and it told me
>  Project not selected to build for this solution configuration
>  I tried changing the configuration in cmake to select and unselect
> Slicer_use_PythonQT and rebuilding but I kept getting the message that the
> project was not selected to be built.  Do I need to delete everything from
> the Slicer4-Superbuild directory before I reconfigure and generate in
> cmake?  Do I need the qSlicerAnnotationsModuleWidgets built to run the MultiVolumeImporter
> module, and if so, what options do I select in cmake to make sure it gets
> built?
>
> Also I am using QT 4.6.3.  Do I need to upgrade to QT 4.7.4 to eliminate
> the error?  If so do I have to delete all of my Slicer4 and
> Slicer4-Superbuild4 directories before I redownload and rebuild?
>
> Any advice on what configuration I need in cmake and what I have to delete
> to make sure I get the latest functionality in Slicer would be greatly
> appreciated.
> '
> Thanks,
>
> Daniel
>
>
>
>  -----Original Message-----
> From: Jean-Christophe Fillion-Robin <jchris.fillionr at kitware.com>
> To: Andriy Fedorov <fedorov at bwh.harvard.edu>
> Cc: danieljohnsonusa <danieljohnsonusa at netscape.net>; slicer-devel <
> slicer-devel at bwh.harvard.edu>
> Sent: Fri, Mar 23, 2012 6:38 pm
> Subject: Re: [slicer-devel] error instantiating python modules in Slicer4
>
>  Andriy, Daniel,
>
> From the two issue mentioned in this email thread:
>
> The first one has been fixed, based on the identified case, no more
> "false" error associated with the loading of PythonQt module will be
> reported.
> See
> https://github.com/Slicer/Slicer/commit/d1ac8c737fa3c5ba737280958329ddf6e7f574d2
>
> The second issue mentioning that a failure to load one module impact the
> loading of other module will be addressed very shortly.
>
> Have a good weekend,
> Jc
>
> On Fri, Mar 23, 2012 at 11:25 AM, Andriy Fedorov <fedorov at bwh.harvard.edu>wrote:
>
>> Daniel,
>>
>> I do not use Windows to build Slicer, but I believe it should build
>> fine with python. I recall there used to be some issues specific to
>> particular versions of VS, but I don't know what is the status.
>>
>> Did you do any modifications to Slicer source code, in particular any
>> python code, in the version you compiled?
>>
>> My understanding is the way python works if there is an error in any
>> of the python modules, this may cause all of the python modules to not
>> be loaded correctly. So the first thing to check is whether you have
>> any issues with the pristine checkout of Slicer.
>>
>> AF
>>
>>
>> On Fri, Mar 23, 2012 at 12:27 AM,  <danieljohnsonusa at netscape.net> wrote:
>> > I have built slicer4 and it all compiles with no errors, but when I go
>> to
>> > start Slicer I get the a message on the command prompt
>> >
>> > no module named slicerannontationsmodulewidgetspythonqt
>> >
>> > I then get the message
>> > Failed to obtain reference to 'qSlicerMainWindow'
>> > No dataprobe frame, cannot create data probe
>> >
>> > It then says
>> > Failed to load scripted pythonqt module class definition
>> MultiVolumeImporter
>> > and then a message saying fail instatiate the module.  The same error
>> > repeats for other pythonqt scripted modules.
>> >
>> > Slicer does run without the scripted python modules available, but I
>> need to
>> > access the MultiVolumeImporter module.  I built from a Windows 7 machine
>> > using VS2008.  I remember that python wasn't supported on Windows7
>> machines
>> > for Slicer3, but I haven't seen any similar disclaimer for Slicer4.
>> Does
>> > anyone have any ideas how this error can be resolved so I can get the
>> > MultiVolumeImporter module to instantiate?
>> >
>> > Thanks,
>> >
>> > Daniel
>> >
>>  > _______________________________________________
>> > slicer-devel mailing list
>> > slicer-devel at bwh.harvard.edu
>> > http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel
>> > To unsubscribe: send email to
>> slicer-devel-request at massmail.spl.harvard.edu
>> > with unsubscribe as the subject
>> _______________________________________________
>> slicer-devel mailing list
>> slicer-devel at bwh.harvard.edu
>> http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel
>> To unsubscribe: send email to
>> slicer-devel-request at massmail.spl.harvard.edu with unsubscribe as the
>> subject
>
>
>
>
> --
> +1 919 869 8849
>
>


-- 
+1 919 869 8849
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://massmail.spl.harvard.edu/public-archives/slicer-devel/attachments/20120324/eca5558d/attachment-0001.html 


More information about the slicer-devel mailing list