I'll get back to you guys if I'm able to work out the other issues. I know a little QT but not really enough to readily diagnose this. The terminal opens the PTY device, and it runs bash with the PTY device as its controlling TTY, but I still don't get anything on the display (it looks just like Anne's screen shot), menu bars don't work, etc. Unfortunately, after this change, it still doesn't appear to be working. Kpty.cpp won't use posix_openpt() unless either HAVE_PTSNAME or TIOCGPTN are defined (this is what causes the fallback to the BSD-style method that doesn't work), and posix_openpt() won't appear in the Cygwin system headers unless you supply the _XOPEN_SOURCE define. +DEFINES += _XOPEN_SOURCE=600 HAVE_POSIX_OPENPT HAVE_PTSNAME HAVE_SYS_TIME_H

DEFINES += HAVE_POSIX_OPENPT HAVE_SYS_TIME_H You can correct that problem with a little change to qmltermwidget/qmltermwidget.pro: That code should come with a great big warning message saying 'your build settings are broken!' - because it's almost certainly not the code you want to be running. The module is falling back on the bad, old BSD-style method (opening all the /dev/pty* devices until it finds one it's able to open) which has been removed from most systems for years.

Yeah there's a problem compiling qmltermwidget/lib/kpty.cpp on Cygwin.īasically, kpty provides platform-abstraction for all the various different ways the OS might support creating a TTY device pair on different systems.

Cool retro term windows