[vtkusers] Very basic question on importing the .h files

[Mike Robertson]

Awesome. Works wonders. One question. I'm running this on os x, of course,
in the X11 environment to be able to use mayavi. Is there any way I can have
two copies of VTK installed, where one runs in quartz and the other in the
X11 environment? I took a look at the quadratic example on the vtk site, and
it's *very* slow in the X11 environment (probably has something to do with
OpenGL...). Would it be faster (and thus worthwhile to compile vtk) in the
primary quartz environment?

mike


~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Michael Robertson
fermion at mac.com
http://thenewcosmos.com


". . . The Egyptians were obsessed with salt. They salted everything,
including their relatives. . ."

- NPR, 2/26/02



> From: Prabhu Ramachandran <prabhu at aero.iitm.ernet.in>
> Date: Sat, 4 May 2002 12:16:23 +0530
> To: Mike Robertson <fermion at mac.com>
> Cc: VTK users list <vtkusers at public.kitware.com>
> Subject: [vtkusers] Very basic question on importing the .h files
> 
>>>>>> "MR" == Mike Robertson <fermion at mac.com> writes:
> 
>   MR> How do I set up my system so that the c++, etc. compilers know
>   MR> where to find such files as ... ?  example.c++:1:
>   MR> vtkQuadric.h: No such file or directory example.c++:2:
> 
> To build off CVS I have a trivial shell script called vtkcc that does
> the job.
> 
> --------------------------------------------------
> #!/bin/sh
> 
> # Edit this file to suit your needs
> 
> VTK_PATH=_path_to_/cvs/VTK
> 
> g++ -I$VTK_PATH -I$VTK_PATH/Common -I$VTK_PATH/Filtering \
> -I$VTK_PATH/Graphics -I$VTK_PATH/Hybrid -I$VTK_PATH/IO \
> -I$VTK_PATH/Imaging -I$VTK_PATH/Patented \
> -I$VTK_PATH/Rendering -I/usr/X11R6/include/X11 \
> -L $VTK_PATH/lib -lvtkCommon -lvtkFiltering -lvtkGraphics \
> -lvtkHybrid -lvtkIO -lvtkImaging -lvtkPatented -lvtkRendering $@
> --------------------------------------------------
> 
> Modify the -L $VTK_PATH/lib to the directory that contains the
> libraries (libvtk*).  Copy the above to a file, make it executable and
> then compile away using vtkcc instead of cc.  Something like so:
> 
> vtkcc test.c -o test -O2 -g
> 
> 
> prabhu
>