Running ObjectIcon on Cygwin requires a little patience ... if your program imports the gui package and opens so much as a dialog, any error can leave you hung in X.
So far I have been kicking off
xwin &
from my objecticon directory and then opening an xterm. Once the mouse gets me a cursor in the xterm (otherwise any typing sends characters to the bit bucket) I immediately run paths.sh as
. ./paths.sh
to get the relevant vars set for the xterm shell. My typical command next is
oit ./my_file.icn -x
and then hope that I do not hang up Cygwin's X-server with a glitch in my ICN code. Or its back to step 1.
It looks as though this will be a head-ache until we are able to run an ObjectIcon application from ivib (the Icon Visual Interface Builder) itself.
