Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs
Date: Mon, 29 Jan 2001 18:32:18 -0600 (CST)
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To: Cygwin Mailing List <cygwin AT sourceware DOT cygnus DOT com>
Subject: Visualization Toolkit (VTK) port to Cygwin
Message-ID: <Pine.HPP.3.96.1010129182148.28810K-100000@hp2.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

The Visualization ToolKit or VTK is a terrific cross-platform
free visualization package that is extremely well-endowed in 
both capability and flexibility. Written in C++, comes with bindings 
for Tcl/Tk, Python, Java in addition to the core C++ bindings.

See http://www.kitware.com/vtk.html for more info.

Working with VTK developers at Kitware, all of the changes needed
to build VTK under Cygwin is now incorporated into the development
tree, which can be checked out using CVS.

The Cygwin port will create bindings for C++ and Tcl/Tk (hence will
support the Tk widgets supplied), but not Java. I'm currently working
on the Python binding using tkinter module (thanks to Jason Tishler
for his work on Cygwin port of Python 2.1a1), and remains to be 
seen. Once that works, I'll forward the minor configuration tweaks
to the VTK developers. 

The code is extremely portable, so that took no work at all. One
line change I believe, and that's because I was too lazy to autoconf
it. Configuration needed quite a bit of change, which is expected.
The trouble came when we tried to build the actual DLLs, and cross
ld on my linux box would eat up about 650 MB of RAM when building
one of the large DLLs! Ended up building the DLL using an intermediate
script that creates a static library, builds the def file and uses
$(CXX) --shared to build the final DLL. For VTK users, see the MakeDLL
script at the top of the source tree.

Regards,
Mumit



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple