>> If you're on Fedora, you need both qt and qt-devel packages. Then simply >> relogin >> and qmake etc. should be in your path. Or, in the terminal session, dive >> into a login shell: >> $ bash - >> This saves on having to relogin. > > I dislike bash, and always switch to tcsh first thing when I install a > new OS. Unfortunately, tcsh seems to have less and less support as time > goes on. I see a startup script for csh in /etc/profile.d/qt.csh, but > I don't know what program calls it. I have all my login and startup > scripts heavily modified from 15 years ago; I dislike desktop > environments, and run a personally-rewritten version of ctwm for my > X11 environment. You might call me "old school". Anyway, I was > a UNIX sysadmin for years in graduate school, and I can resolve these > issues one way or another. . .
Understood. X11 is a nice concept, but the execution IMHO is severely out of sync with everyday basic requirements of applications. To get things looking good under X11, you pretty much can't use Xlib for anything else than basic event and window management, and blitting. Xlib's drawing calls are useless as you have already noticed, there's zero printing support, server-side font handling is best ignored, etc. All this was, in fact, severely increasing the workload of Qt developers in the early days of Qt (up to Qt 3). Qt had to pretty much take over all rendering in order to look good on X11 -- on par with what'd be considered native on modern win32 and OS X. Then the trolls (Qt devs) figured that their raster engine was good enough to match native performance on other platforms, and these days Qt does all the rendering itself, and lots of compositing too -- that way if you paint something on X11 it'll look exactly the same, down to image buffer bits, on Windows and OS X as long as same fonts are available. Cheers, Kuba _______________________________________________ Xcircuit-dev mailing list [email protected] http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
