Hi Jérôme, The plugin has to be built against a paraview build that uses the same libraries that the paraview release build was built against.
The list of libraries/versions that Berk used to build the releases is here: http://www.paraview.org/Wiki/ParaView_Binaries Old (including 4.3.5) versions of Qt can be found here: ftp://ftp.trolltech.no/qt/source/ cheers, Dave DeMarle On Fri, Dec 12, 2008 at 2:56 AM, Jérôme <[email protected]> wrote: > Hi, > > Thanks to the mailing list, I compiled successfully a number of > plugins for paraview 3.4. Today, the version of Qt is 4.4, and > everything goes well on my different computers (Fedora 9 and Win XP > SP3). > > Now, I want to distribute my plugins on 'non-development' config, that > is, with the website-available binaries of ParaView 3.4. > When loading the plugin, I got a message '... is not a valid Qt > plugin'. Then I tried different built settings (Release/Debug), > without success. > > I think that the downloadable binaries are built with Qt-4.3, not 4.4 > -that justifies the cmake warning-, and maybe this is the source of > the problem. > - Can someone tell me if I am wrong ? > - Have I to distribute my own ParaView built or is there a hack for that ? > - If I have to downgrade Qt to 4.3, where can I find the MS Windows package ? > > Thanks for your time, > > Jérôme > _______________________________________________ > ParaView mailing list > [email protected] > http://www.paraview.org/mailman/listinfo/paraview > -- David E DeMarle Kitware, Inc. R&D Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 _______________________________________________ ParaView mailing list [email protected] http://www.paraview.org/mailman/listinfo/paraview
