Hi Bertwim,

This worked for me - cmake now finds Qt and builds the plugin. Many thanks.

It isn't clear to me why it previously worked with PV 4.1.0 but not with 4.2.0. 
I guess it doesn't matter as long as it's working :)

Kind regards,
Jim

________________________________
From: ParaView [mailto:[email protected]] On Behalf Of B.W.H. van 
Beest
Sent: 07 October 2014 17:56
To: [email protected]
Subject: EXTERNAL: Re: [Paraview] Problem building plugin against ParaView 4.2.0

Jim,

I had similar issues you describe. They were gone when I made sure that, before 
actually calling cmake,  the right 'qmake' was in the PATH  (i.e. 'which qmake' 
 points to the qmake of the AQT-version your expect).  This assumes that you do 
have a Qt installation which is complete.
In other words:
1. ensure qmake of the Qt distribution you expect is in your path
2. ensure your paraview build directory is clean ( rm -rf   <path>/build/* )
3. start the cmake configuration.

Hope this works for you too,

Regards,
Bertwim

On 10/07/2014 03:25 PM, [email protected]<mailto:[email protected]> wrote:

Hello everyone,

I am trying to build a file reader plugin against ParaView 4.2.0 and have been 
experiencing some difficulties. Qt is not found by cmake during the build 
process causing it to fail.

To illustrate the issue, I created the following simplified CMakeLists.txt file:

    CMAKE_MINIMUM_REQUIRED
    FIND_PACKAGE(ParaView REQUIRED)
    INCLUDE(${PARAVIEW_USE_FILE})

When I call cmake with ParaView_DIR pointing at my 4.1.0 build Qt is found, but 
with 4.2.0 Qt is NOT found.

ParaView was built using Superbuild and Qt was built as part of that process. 
Should Qt be detected from ParaViewConfig.cmake?

Is this a change in behaviour between 4.1.0 and 4.2.0? Do I somehow need to 
specify the location of Qt manually?

Any ideas?

Thank you,
Jim


Jim Eliot
High Performance Computing Group
AWE, Aldermaston, Reading, RG7 4PR


___________________________________________________ 
____________________________ The information in this email and in any 
attachment(s) is commercial in confidence. If you are not the named 
addressee(s) or if you receive this email in error then any distribution, 
copying or use of this communication or the information in it is strictly 
prohibited. Please notify us immediately by email at 
admin.internet(at)awe.co.uk, and then delete this message from your computer. 
While attachments are virus checked, AWE plc does not accept any liability in 
respect of any virus which is not detected. AWE Plc Registered in England and 
Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR




_______________________________________________

Powered by www.kitware.com<http://www.kitware.com>



Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html



Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView



Follow this link to subscribe/unsubscribe:

http://public.kitware.com/mailman/listinfo/paraview



___________________________________________________
____________________________

The information in this email and in any attachment(s) is
commercial in confidence. If you are not the named addressee(s)
or
if you receive this email in error then any distribution, copying or
use of this communication or the information in it is strictly
prohibited. Please notify us immediately by email at
admin.internet(at)awe.co.uk, and then delete this message from
your computer. While attachments are virus checked, AWE plc
does not accept any liability in respect of any virus which is not
detected.

AWE Plc
Registered in England and Wales
Registration No 02763902
AWE, Aldermaston, Reading, RG7 4PR
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Reply via email to