[Paraview-developers] Home make plugin

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Wed Sep 30 10:06:05 EDT 2015 

Qt5 support is still experimental in ParaView. I'd suggest sticking
with Qt4. Also start with a clean build directory to avoid conflicting
with Qt5 previously built.

On Wed, Sep 30, 2015 at 12:05 AM, Chiranjib Sur <sur.chiranjib at gmail.com> wrote:
> Utkarsh,
> Thanks,
> Looks like the build error is coming majorly from QVis.
>
> make[2]: ***
> [Plugins/PointSprite/Qvis/CMakeFiles/vtkQvis.dir/QvisColorGridWidget.cpp.o]
> Error 1
> make[2]: Target `Plugins/PointSprite/Qvis/CMakeFiles/vtkQvis.dir/build' not
> remade because of errors.
> make[1]: *** [Plugins/PointSprite/Qvis/CMakeFiles/vtkQvis.dir/all] Error 2
>
> I am attaching the complete success+error log. Hope to get some pointer.
> FYI, I have enabled qt5 while creating the Makefile(s) from super-build
>
> Thanks,
> Chiranjib
>
>
>
> On Tue, Sep 29, 2015 at 7:07 PM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>>
>> Chiranjib,
>>
>> In your build directory do this:
>>
>> > cd paraview/src/paraview-build
>> > make
>>
>> Now when the it fails, post that error. Your ParaView build is failing
>> and that's what's causing the problem. BTW "make -i" simply ignores
>> build errors so you'll only get more and more convoluted error
>> messages that will keep you focusing away from the root problem.
>>
>> Utkarsh
>>
>> On Tue, Sep 29, 2015 at 7:41 AM, Chiranjib Sur <sur.chiranjib at gmail.com>
>> wrote:
>> > Hi,
>> > I tried the 'make -i" option and got following error message. May be
>> > this
>> > will help to debug the issue further
>> >
>> > CMake Error at cmake_install.cmake:51 (file):
>> >   file INSTALL cannot find
>> >
>> >
>> > "/glb/home/incsu0/ir1/SPH/ParaView-4.4-SuperBuild/Sept-29/paraview/src/paraview-build/lib/libvtkPVPythonCatalystPython27D-pv4.4.so.1".
>> >
>> >
>> > Thanks,
>> > Chiranjib
>> >
>> > On Tue, Sep 29, 2015 at 4:33 PM, Chiranjib Sur <sur.chiranjib at gmail.com>
>> > wrote:
>> >>
>> >> Hi,
>> >> While I was trying to do this superbuild I got the following error
>> >> while
>> >> running gmake.
>> >>
>> >>
>> >> [ 78%] Building CXX object
>> >>
>> >> VTK/Wrapping/Python/CMakeFiles/vtkPVServerManagerCorePython.dir/vtkPVServerManagerCorePythonInit.cxx.o
>> >> In file included from
>> >>
>> >> /glb/home/incsu0/ir1/SPH/ParaView-4.4-SuperBuild/Sept-29/install/include/python2.7/Python.h:126,
>> >>                  from
>> >>
>> >> /glb/home/incsu0/ir1/SPH/ParaView-4.4-SuperBuild/Sept-29/paraview/src/paraview/VTK/Utilities/Python/vtkPython.h:79,
>> >>                  from
>> >>
>> >> /glb/home/incsu0/ir1/SPH/ParaView-4.4-SuperBuild/Sept-29/paraview/src/paraview-build/VTK/Wrapping/Python/vtkPVServerManagerCorePythonInit.cxx:2:
>> >>
>> >>
>> >> /glb/home/incsu0/ir1/SPH/ParaView-4.4-SuperBuild/Sept-29/install/include/python2.7/modsupport.h:27:
>> >> warning: ?PyArg_ParseTuple? is an unrecognized format function type
>> >> Linking CXX shared module ../../../lib/vtkPVServerManagerCorePython.so
>> >> [ 78%] Built target vtkPVServerManagerCorePython
>> >> gmake[4]: Target `all' not remade because of errors.
>> >> gmake[3]: *** [all] Error 2
>> >> gmake[3]: Target `default_target' not remade because of errors.
>> >> CMake Error at
>> >>
>> >> /glb/home/incsu0/ir1/SPH/ParaView-4.4-SuperBuild/Sept-29/pv-paraview-build.cmake:33
>> >> (message):
>> >>   Failed with exit code 2
>> >>
>> >>
>> >> To start with I was trying to build the following components
>> >>
>> >> [  8%] Built target bzip2
>> >> [ 17%] Built target zlib
>> >> [ 25%] Built target freetype
>> >> [ 33%] Built target libxml2
>> >> [ 40%] Built target fontconfig
>> >> [ 48%] Built target szip
>> >> [ 55%] Built target hdf5
>> >> [ 62%] Built target mpi
>> >> [ 70%] Built target png
>> >> [ 77%] Built target python
>> >> [ 85%] Built target numpy
>> >> [ 93%] Built target qt5
>> >> [ 93%] Performing update step for 'paraview'
>> >> Already on 'master'
>> >> Your branch is up-to-date with 'origin/master'.
>> >> [ 94%] Performing configure step for 'paraview'
>> >> -- Setting build type to 'Debug' as none was specified.
>> >>
>> >>
>> >> Any clue how to handle this?
>> >>
>> >> On Wed, Sep 23, 2015 at 8:58 PM, Felipe Bordeu
>> >> <felipe.bordeu at ec-nantes.fr> wrote:
>> >>>
>> >>>
>> >>> -----BEGIN PGP SIGNED MESSAGE-----
>> >>> Hash: SHA1
>> >>>
>> >>> Hi Utkarsh,
>> >>>
>> >>> for the moment I have this:
>> >>>
>> >>> I modified the ParaView Super Build  sources :
>> >>>     add the line "include(pxdmfreader)" to the CMakeLists.txt
>> >>>     and add a revision in the file versions.cmake
>> >>> ("add_customizable_revision(pxdmfreader...")
>> >>>
>> >>> add 2 file the Project directory (in the way as the vistrails plugin)
>> >>>     pxdmfreader.cmake
>> >>>     install_pxdmfreader.cmake
>> >>>
>> >>> the install_pxdmfreader.cmake is responsible of making the zip files.
>> >>>
>> >>>
>> >>>
>> >>> Now I configure the super build and I enable the plugin. The plugin is
>> >>> compiled and a zip/tar.gz is generated (tested in linux/osx)
>> >>>
>> >>> is this the correct way to go???
>> >>> is this enough to be compatible with the binary version of ParaView??
>> >>>
>> >>> It is normal that every time I type 'make' in the superbuild build
>> >>> directory a configuration process (cmake) on the
>> >>> paraview/src/paraview-build/ is executed?? This is verry slow. I made
>> >>> changes only in my plugin.
>> >>>
>> >>> Now I'm working in detecting/building the dependencies correctly
>> >>> (blas,
>> >>> xdmf2/3, boost, zlib).
>> >>>
>> >>> Thanks
>> >>>
>> >>> Felipe
>> >>>
>> >>>
>> >>>
>> >>> Le 21/09/2015 16:39, Utkarsh Ayachit a écrit :
>> >>> > Felipe,
>> >>> >
>> >>> >> For the moment we don't have a license (I have to read the BSD
>> >>> >> license).
>> >>> >
>> >>> > Okay. You should figure this part out sooner rather than later.
>> >>> >
>> >>> >
>> >>> >> For building the plugin we use :
>> >>> >> boost (because the Xdmf3lib reader use it)
>> >>> >> latex to build the pdf of the documentation and include it in the
>> >>> >> .so
>> >>> file.
>> >>> >> I added a "save documentation to disk" button in the plugin . (this
>> >>> in not
>> >>> >> mandatory, I can disable this)
>> >>> >> blas (cblas of just blas): we do intensive computation so we really
>> >>> >> need
>> >>> >> blas. (I have a "no_blas" flag to compile the plugin on
>> >>> >> android/IOS).
>> >>> >
>> >>> >
>> >>> > ParaView Superbuild doesn't have "blas". You'll need to extend the
>> >>> > superbuild to teach it how to build & package that as well.
>> >>> >
>> >>> >> Now my question is how to handle releases and compilation errors??
>> >>> >> Do I have to put the sources in a github?
>> >>> >
>> >>> > Yes, you can create a merge-request on the ParaVIew supbuild
>> >>> > gitlab[1]
>> >>> > . We can do builds on all platforms from a MR that you can then use
>> >>> > to
>> >>> > track down any build issues that may be introduced as a result of
>> >>> > the
>> >>> > changes.
>> >>> >
>> >>> > Utkarsh
>> >>> >
>> >>> >
>> >>> > [1] https://gitlab.kitware.com/paraview/paraview-superbuild
>> >>>
>> >>>
>> >>> - --
>> >>> Felipe Bordeu Weldt
>> >>> Ingénieur de Recherche
>> >>> - -------------------------------------
>> >>> Tél. : 33 (0)2 40 37 16 57
>> >>> Fax. : 33 (0)2 40 74 74 06
>> >>> Felipe.Bordeu at ec-nantes.fr
>> >>> Institut GeM - UMR CNRS 6183
>> >>> École Centrale Nantes
>> >>> 1 Rue de La Noë, 44321 Nantes, FRANCE
>> >>> - -------------------------------------
>> >>> -----BEGIN PGP SIGNATURE-----
>> >>> Version: GnuPG v2.0.22 (GNU/Linux)
>> >>>
>> >>> iQEcBAEBAgAGBQJWAsUrAAoJEE/fMfNgU9/D0zcIAMhE6kv4u0CCWdg4Kn51d3Fu
>> >>> KBtey3PR+p8O/dGHbAjpa5W5zRiTzltc6FVAVDCYizDN4ovA+pZjunFqPFLntMdy
>> >>> 1NewGfJ/EtflONbMI+/7KZI1iPf6O+ebeyBEPmrv9uNAzQAnRECGEC4dU6kHndbE
>> >>> 5Cz7xK0HK+wR1xAm8J7WsZS24ySyBaNQRPPlIdZjc/lE2fOC/0vrb5com7EpJFAr
>> >>> +JHmYI1+EAZTZw6wVdj8CgBY57LFlzq0V/JsJ10gY8r+/w7meR1IZvOMSL64sqqU
>> >>> Q397ltZFWfTf8K02FA5coTtg0dwpXKsBXuy6xzIIrNOJABryW9aa2DPoTVzzo0k=
>> >>> =Feu6
>> >>> -----END PGP SIGNATURE-----
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> Powered by www.kitware.com
>> >>>
>> >>> Visit other Kitware open-source projects at
>> >>> http://www.kitware.com/opensource/opensource.html
>> >>>
>> >>> Search the list archives at:
>> >>> http://markmail.org/search/?q=Paraview-developers
>> >>>
>> >>> Follow this link to subscribe/unsubscribe:
>> >>> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>
>> >>
>> >
>
>

More information about the Paraview-developers mailing list