Re: [Paraview] Building a distributable development tree

2010-04-07 Thread Dave Partyka 
Hi Ben,

You need to turn on PARAVIEW_INSTALL_DEVELOPMENT to get the include
directories. Is that the case? The ParaViewConfig.cmake file should be in
the lib/paraview-x.x/ directory. I will try testing this out. The install
rule for paraview.qch needs logic to disable it when there is no gui. I'll
fix that right now.

Thanks for your feedback!

On Tue, Apr 6, 2010 at 7:51 PM, Ben Medina ben.med...@gmail.com wrote:

 Hello all,

 I've been trying to generate a development tree of ParaView (based on
 CVS head as of a few hours ago) that I can distribute to other
 in-house developers so that they don't have to build ParaView
 themselves. I've been following the instructions here:
 http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView

 I have set the CMake variables as described (with
 PARAVIEW_BUILD_QT_GUI OFF). Building and packaging works correctly,
 but the resultant tarball (built via cpack -G TGZ --config
 {ParaViewBuildDir}/Servers/Executables/CPackParaViewServersConfig.cmake)
 contains only lib and bin directories; there is no include directory,
 nor a ParaViewConfig.cmake file.

 make install seems more promising, as I do end up with a more complete
 tree. However, the install fails with the following error:
 CMake Error at Documentation/cmake_install.cmake:36 (FILE):
  file INSTALL cannot find

  
 /home/ben/3rdpartylibs/paraview/3.7b/unpacked-download-directory/linuxg29x64.26/Documentation/paraview.qch.
 Call Stack (most recent call first):
  cmake_install.cmake:95 (INCLUDE)

 Can anyone tell what's going wrong?

 Thanks,
 Ben
 ___
 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://www.paraview.org/mailman/listinfo/paraview

___
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://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Building a distributable development tree

2010-04-07 Thread Dave Partyka 
Hi Ben,

If you do an update it shouldn't attempt to install the qch file. Also so
you know, the ParaViewConfig.cmake file doesn't get installed if
PARAVIEW_INSTALL_DEVELOPMENT is turned off.

Let me know if you have anymore issues. Thanks!

On Wed, Apr 7, 2010 at 9:01 AM, Dave Partyka dave.part...@kitware.comwrote:

 Hi Ben,

 You need to turn on PARAVIEW_INSTALL_DEVELOPMENT to get the include
 directories. Is that the case? The ParaViewConfig.cmake file should be in
 the lib/paraview-x.x/ directory. I will try testing this out. The install
 rule for paraview.qch needs logic to disable it when there is no gui. I'll
 fix that right now.

 Thanks for your feedback!


 On Tue, Apr 6, 2010 at 7:51 PM, Ben Medina ben.med...@gmail.com wrote:

 Hello all,

 I've been trying to generate a development tree of ParaView (based on
 CVS head as of a few hours ago) that I can distribute to other
 in-house developers so that they don't have to build ParaView
 themselves. I've been following the instructions here:
 http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView

 I have set the CMake variables as described (with
 PARAVIEW_BUILD_QT_GUI OFF). Building and packaging works correctly,
 but the resultant tarball (built via cpack -G TGZ --config
 {ParaViewBuildDir}/Servers/Executables/CPackParaViewServersConfig.cmake)
 contains only lib and bin directories; there is no include directory,
 nor a ParaViewConfig.cmake file.

 make install seems more promising, as I do end up with a more complete
 tree. However, the install fails with the following error:
 CMake Error at Documentation/cmake_install.cmake:36 (FILE):
  file INSTALL cannot find

  
 /home/ben/3rdpartylibs/paraview/3.7b/unpacked-download-directory/linuxg29x64.26/Documentation/paraview.qch.
 Call Stack (most recent call first):
  cmake_install.cmake:95 (INCLUDE)

 Can anyone tell what's going wrong?

 Thanks,
 Ben
 ___
 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://www.paraview.org/mailman/listinfo/paraview



___
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://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Building a distributable development tree

2010-04-07 Thread Ben Medina 
Dave,
I'm updating now, and I'll let you know how it goes.

A related question is how to build the dev tree on Windows. How do I
get both debug and release versions of the libraries into one package?
Or is it safe to just include the release version?

Thanks,
Ben

Note: I didn't mean to take this discussion off-list, sorry.

On Wed, Apr 7, 2010 at 11:18 AM, Dave Partyka dave.part...@kitware.com wrote:
 Hi Ben,
 Try updating again when you get a chance. I found some CMake code that was
 overriding the Development Component thus causing it to not get installed.
 Thanks!

 On Wed, Apr 7, 2010 at 11:55 AM, Ben Medina ben.med...@gmail.com wrote:

 Thanks, Dave! I'll try out the qch fix soon. Other than that, make
 install seems to produce exactly what I want, so I'll use that for
 now.

 I do have PARAVIEW_INSTALL_DEVELOPMENT turned on, but the resulting
 tar.gz is not usable for development. My CMake cache is attached.

 Thank,
 Ben

 On Wed, Apr 7, 2010 at 6:22 AM, Dave Partyka dave.part...@kitware.com
 wrote:
  Hi Ben,
  If you do an update it shouldn't attempt to install the qch file. Also
  so
  you know, the ParaViewConfig.cmake file doesn't get installed if
  PARAVIEW_INSTALL_DEVELOPMENT is turned off.
  Let me know if you have anymore issues. Thanks!
 
  On Wed, Apr 7, 2010 at 9:01 AM, Dave Partyka dave.part...@kitware.com
  wrote:
 
  Hi Ben,
  You need to turn on PARAVIEW_INSTALL_DEVELOPMENT to get the include
  directories. Is that the case? The ParaViewConfig.cmake file should
  be in
  the lib/paraview-x.x/ directory. I will try testing this out. The
  install
  rule for paraview.qch needs logic to disable it when there is no gui.
  I'll
  fix that right now.
  Thanks for your feedback!
 
  On Tue, Apr 6, 2010 at 7:51 PM, Ben Medina ben.med...@gmail.com
  wrote:
 
  Hello all,
 
  I've been trying to generate a development tree of ParaView (based on
  CVS head as of a few hours ago) that I can distribute to other
  in-house developers so that they don't have to build ParaView
  themselves. I've been following the instructions here:
 
  http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView
 
  I have set the CMake variables as described (with
  PARAVIEW_BUILD_QT_GUI OFF). Building and packaging works correctly,
  but the resultant tarball (built via cpack -G TGZ --config
 
  {ParaViewBuildDir}/Servers/Executables/CPackParaViewServersConfig.cmake)
  contains only lib and bin directories; there is no include directory,
  nor a ParaViewConfig.cmake file.
 
  make install seems more promising, as I do end up with a more complete
  tree. However, the install fails with the following error:
  CMake Error at Documentation/cmake_install.cmake:36 (FILE):
   file INSTALL cannot find
 
 
   /home/ben/3rdpartylibs/paraview/3.7b/unpacked-download-directory/linuxg29x64.26/Documentation/paraview.qch.
  Call Stack (most recent call first):
   cmake_install.cmake:95 (INCLUDE)
 
  Can anyone tell what's going wrong?
 
  Thanks,
  Ben
  ___
  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://www.paraview.org/mailman/listinfo/paraview
 
 
 


___
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://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Building a distributable development tree

2010-04-07 Thread Dave Partyka 
I don't think you can do both. Specifying -C Release/Debug tells cpack
which directory to grab everything out of. Also if you do Debug I don't
believe there are install rules to grab the .pdb symbol files. Though, that
probably wouldn't be hard to do.

On Wed, Apr 7, 2010 at 5:02 PM, Ben Medina ben.med...@gmail.com wrote:

 Dave,
 I'm updating now, and I'll let you know how it goes.

 A related question is how to build the dev tree on Windows. How do I
 get both debug and release versions of the libraries into one package?
 Or is it safe to just include the release version?

 Thanks,
 Ben

 Note: I didn't mean to take this discussion off-list, sorry.

 On Wed, Apr 7, 2010 at 11:18 AM, Dave Partyka dave.part...@kitware.com
 wrote:
  Hi Ben,
  Try updating again when you get a chance. I found some CMake code that
 was
  overriding the Development Component thus causing it to not get
 installed.
  Thanks!
 
  On Wed, Apr 7, 2010 at 11:55 AM, Ben Medina ben.med...@gmail.com
 wrote:
 
  Thanks, Dave! I'll try out the qch fix soon. Other than that, make
  install seems to produce exactly what I want, so I'll use that for
  now.
 
  I do have PARAVIEW_INSTALL_DEVELOPMENT turned on, but the resulting
  tar.gz is not usable for development. My CMake cache is attached.
 
  Thank,
  Ben
 
  On Wed, Apr 7, 2010 at 6:22 AM, Dave Partyka dave.part...@kitware.com
  wrote:
   Hi Ben,
   If you do an update it shouldn't attempt to install the qch file. Also
   so
   you know, the ParaViewConfig.cmake file doesn't get installed if
   PARAVIEW_INSTALL_DEVELOPMENT is turned off.
   Let me know if you have anymore issues. Thanks!
  
   On Wed, Apr 7, 2010 at 9:01 AM, Dave Partyka 
 dave.part...@kitware.com
   wrote:
  
   Hi Ben,
   You need to turn on PARAVIEW_INSTALL_DEVELOPMENT to get the include
   directories. Is that the case? The ParaViewConfig.cmake file should
   be in
   the lib/paraview-x.x/ directory. I will try testing this out. The
   install
   rule for paraview.qch needs logic to disable it when there is no gui.
   I'll
   fix that right now.
   Thanks for your feedback!
  
   On Tue, Apr 6, 2010 at 7:51 PM, Ben Medina ben.med...@gmail.com
   wrote:
  
   Hello all,
  
   I've been trying to generate a development tree of ParaView (based
 on
   CVS head as of a few hours ago) that I can distribute to other
   in-house developers so that they don't have to build ParaView
   themselves. I've been following the instructions here:
  
  
 http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView
  
   I have set the CMake variables as described (with
   PARAVIEW_BUILD_QT_GUI OFF). Building and packaging works correctly,
   but the resultant tarball (built via cpack -G TGZ --config
  
  
 {ParaViewBuildDir}/Servers/Executables/CPackParaViewServersConfig.cmake)
   contains only lib and bin directories; there is no include
 directory,
   nor a ParaViewConfig.cmake file.
  
   make install seems more promising, as I do end up with a more
 complete
   tree. However, the install fails with the following error:
   CMake Error at Documentation/cmake_install.cmake:36 (FILE):
file INSTALL cannot find
  
  
  
  
 /home/ben/3rdpartylibs/paraview/3.7b/unpacked-download-directory/linuxg29x64.26/Documentation/paraview.qch.
   Call Stack (most recent call first):
cmake_install.cmake:95 (INCLUDE)
  
   Can anyone tell what's going wrong?
  
   Thanks,
   Ben
   ___
   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://www.paraview.org/mailman/listinfo/paraview
  
  
  
 
 

___
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://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Building a distributable development tree

2010-04-07 Thread Ben Medina 
Thanks. I don't care about the pdb files for now. I just want linking
and running to work for them when they build debug versions of our
app. I guess I'll just tell them to try linking against the release
build I'm providing, and if it fails, they'll have to build ParaView
themselves.

What are you guys planning on shipping for 3.8? Just the release libraries?

- Ben

On Wed, Apr 7, 2010 at 2:11 PM, Dave Partyka dave.part...@kitware.com wrote:
 I don't think you can do both. Specifying -C Release/Debug tells cpack
 which directory to grab everything out of. Also if you do Debug I don't
 believe there are install rules to grab the .pdb symbol files. Though, that
 probably wouldn't be hard to do.

 On Wed, Apr 7, 2010 at 5:02 PM, Ben Medina ben.med...@gmail.com wrote:

 Dave,
 I'm updating now, and I'll let you know how it goes.

 A related question is how to build the dev tree on Windows. How do I
 get both debug and release versions of the libraries into one package?
 Or is it safe to just include the release version?

 Thanks,
 Ben

 Note: I didn't mean to take this discussion off-list, sorry.

 On Wed, Apr 7, 2010 at 11:18 AM, Dave Partyka dave.part...@kitware.com
 wrote:
  Hi Ben,
  Try updating again when you get a chance. I found some CMake code that
  was
  overriding the Development Component thus causing it to not get
  installed.
  Thanks!
 
  On Wed, Apr 7, 2010 at 11:55 AM, Ben Medina ben.med...@gmail.com
  wrote:
 
  Thanks, Dave! I'll try out the qch fix soon. Other than that, make
  install seems to produce exactly what I want, so I'll use that for
  now.
 
  I do have PARAVIEW_INSTALL_DEVELOPMENT turned on, but the resulting
  tar.gz is not usable for development. My CMake cache is attached.
 
  Thank,
  Ben
 
  On Wed, Apr 7, 2010 at 6:22 AM, Dave Partyka dave.part...@kitware.com
  wrote:
   Hi Ben,
   If you do an update it shouldn't attempt to install the qch file.
   Also
   so
   you know, the ParaViewConfig.cmake file doesn't get installed if
   PARAVIEW_INSTALL_DEVELOPMENT is turned off.
   Let me know if you have anymore issues. Thanks!
  
   On Wed, Apr 7, 2010 at 9:01 AM, Dave Partyka
   dave.part...@kitware.com
   wrote:
  
   Hi Ben,
   You need to turn on PARAVIEW_INSTALL_DEVELOPMENT to get the include
   directories. Is that the case? The ParaViewConfig.cmake file
   should
   be in
   the lib/paraview-x.x/ directory. I will try testing this out. The
   install
   rule for paraview.qch needs logic to disable it when there is no
   gui.
   I'll
   fix that right now.
   Thanks for your feedback!
  
   On Tue, Apr 6, 2010 at 7:51 PM, Ben Medina ben.med...@gmail.com
   wrote:
  
   Hello all,
  
   I've been trying to generate a development tree of ParaView (based
   on
   CVS head as of a few hours ago) that I can distribute to other
   in-house developers so that they don't have to build ParaView
   themselves. I've been following the instructions here:
  
  
   http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView
  
   I have set the CMake variables as described (with
   PARAVIEW_BUILD_QT_GUI OFF). Building and packaging works correctly,
   but the resultant tarball (built via cpack -G TGZ --config
  
  
   {ParaViewBuildDir}/Servers/Executables/CPackParaViewServersConfig.cmake)
   contains only lib and bin directories; there is no include
   directory,
   nor a ParaViewConfig.cmake file.
  
   make install seems more promising, as I do end up with a more
   complete
   tree. However, the install fails with the following error:
   CMake Error at Documentation/cmake_install.cmake:36 (FILE):
    file INSTALL cannot find
  
  
  
    /home/ben/3rdpartylibs/paraview/3.7b/unpacked-download-directory/linuxg29x64.26/Documentation/paraview.qch.
   Call Stack (most recent call first):
    cmake_install.cmake:95 (INCLUDE)
  
   Can anyone tell what's going wrong?
  
   Thanks,
   Ben
   ___
   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://www.paraview.org/mailman/listinfo/paraview
  
  
  
 
 


___
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://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Building a distributable development tree

2010-04-07 Thread Dave Partyka 
Yes the development install packages we provide will be release.

On Wed, Apr 7, 2010 at 5:38 PM, Ben Medina ben.med...@gmail.com wrote:

 Thanks. I don't care about the pdb files for now. I just want linking
 and running to work for them when they build debug versions of our
 app. I guess I'll just tell them to try linking against the release
 build I'm providing, and if it fails, they'll have to build ParaView
 themselves.

 What are you guys planning on shipping for 3.8? Just the release libraries?

 - Ben

 On Wed, Apr 7, 2010 at 2:11 PM, Dave Partyka dave.part...@kitware.com
 wrote:
  I don't think you can do both. Specifying -C Release/Debug tells cpack
  which directory to grab everything out of. Also if you do Debug I don't
  believe there are install rules to grab the .pdb symbol files. Though,
 that
  probably wouldn't be hard to do.
 
  On Wed, Apr 7, 2010 at 5:02 PM, Ben Medina ben.med...@gmail.com wrote:
 
  Dave,
  I'm updating now, and I'll let you know how it goes.
 
  A related question is how to build the dev tree on Windows. How do I
  get both debug and release versions of the libraries into one package?
  Or is it safe to just include the release version?
 
  Thanks,
  Ben
 
  Note: I didn't mean to take this discussion off-list, sorry.
 
  On Wed, Apr 7, 2010 at 11:18 AM, Dave Partyka dave.part...@kitware.com
 
  wrote:
   Hi Ben,
   Try updating again when you get a chance. I found some CMake code that
   was
   overriding the Development Component thus causing it to not get
   installed.
   Thanks!
  
   On Wed, Apr 7, 2010 at 11:55 AM, Ben Medina ben.med...@gmail.com
   wrote:
  
   Thanks, Dave! I'll try out the qch fix soon. Other than that, make
   install seems to produce exactly what I want, so I'll use that for
   now.
  
   I do have PARAVIEW_INSTALL_DEVELOPMENT turned on, but the resulting
   tar.gz is not usable for development. My CMake cache is attached.
  
   Thank,
   Ben
  
   On Wed, Apr 7, 2010 at 6:22 AM, Dave Partyka 
 dave.part...@kitware.com
   wrote:
Hi Ben,
If you do an update it shouldn't attempt to install the qch file.
Also
so
you know, the ParaViewConfig.cmake file doesn't get installed if
PARAVIEW_INSTALL_DEVELOPMENT is turned off.
Let me know if you have anymore issues. Thanks!
   
On Wed, Apr 7, 2010 at 9:01 AM, Dave Partyka
dave.part...@kitware.com
wrote:
   
Hi Ben,
You need to turn on PARAVIEW_INSTALL_DEVELOPMENT to get the
 include
directories. Is that the case? The ParaViewConfig.cmake file
should
be in
the lib/paraview-x.x/ directory. I will try testing this out. The
install
rule for paraview.qch needs logic to disable it when there is no
gui.
I'll
fix that right now.
Thanks for your feedback!
   
On Tue, Apr 6, 2010 at 7:51 PM, Ben Medina ben.med...@gmail.com
wrote:
   
Hello all,
   
I've been trying to generate a development tree of ParaView
 (based
on
CVS head as of a few hours ago) that I can distribute to other
in-house developers so that they don't have to build ParaView
themselves. I've been following the instructions here:
   
   
   
 http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView
   
I have set the CMake variables as described (with
PARAVIEW_BUILD_QT_GUI OFF). Building and packaging works
 correctly,
but the resultant tarball (built via cpack -G TGZ --config
   
   
   
 {ParaViewBuildDir}/Servers/Executables/CPackParaViewServersConfig.cmake)
contains only lib and bin directories; there is no include
directory,
nor a ParaViewConfig.cmake file.
   
make install seems more promising, as I do end up with a more
complete
tree. However, the install fails with the following error:
CMake Error at Documentation/cmake_install.cmake:36 (FILE):
 file INSTALL cannot find
   
   
   
   
  
 /home/ben/3rdpartylibs/paraview/3.7b/unpacked-download-directory/linuxg29x64.26/Documentation/paraview.qch.
Call Stack (most recent call first):
 cmake_install.cmake:95 (INCLUDE)
   
Can anyone tell what's going wrong?
   
Thanks,
Ben
___
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://www.paraview.org/mailman/listinfo/paraview
   
   
   
  
  
 
 

___
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://www.paraview.org/mailman/listinfo/paraview