From octave-graphics-request at bevo dot che dot wisc dot edu Sun Mar 14 08:15:59 2004 Subject: Re: Octaviz From: Paul Kienzle To: Dragan Tubic Cc: octave-graphics at bevo dot che dot wisc dot edu Date: Sun, 14 Mar 2004 09:15:35 -0500 On Mar 14, 2004, at 12:06 AM, Dragan Tubic wrote: > Hi all, > > There is a new version of octaviz, visualization system for Octave > (http://octaviz.sourceforge.net/). This version does not introduce new > functionalities; major changes are related to > configuration/compilation. > Octaviz now can be configured using CMake and properly installed. VTK > classes > are not wrapped into individual .oct files any more. There are only > ~10 .oct > files which reduces compilation time from couple of hours to about 5 > minutes. Great! How big are the oct-files? Smaller than 30-50 Mb I hope! > ~60 VTK Python examples are converted and included in Octaviz, Finally, > octaviz compiles under CygWin but it does NOT run due to some strange > fork/opendl problem in cygwin that involves base address in dlls. If > anyone > knows how to solve it please let me know. I found this happening on some machines and not others. I tried using rebase to avoid conflicts but to no avail. My solution was to have an option not to fork, which meant that my octave process could only service one connection. The better solution is to avoid fork altogether and to instead use a higher level interface, which on windows systems calls CreateProcess or _popen and on unix calls fork-exec. I've done a little bit of this for octave, but I don't remember if any of it worked its way back into the octave tree. I find the source code for Ruby to be an excellent source for examples of working with Windows API. Unfortunately the process handling code gets a little complicated because they are trying to emulate child PIDs and process control, which is presumably more elaborate support than VTK needs. Good luck! Paul Kienzle pkienzle at users dot sf dot net