Home [ade] cookies

QtCreator on OpenSolaris

At FSCONS I attended a talk by Johan Thelin — good to see someone whose blog I’ve followed for a long time, but whom I’d never met before — about QtCreator. The talk itself was a bit simple, more a “how to get the toolchain going” than a “deep secrets of Qt creator.” But because I was there I decided to update the OpenSolaris specfile for qtcreator to version 1.2.90 (the latest version for which a source download is available), and it took remarkably little effort to get it going.

Several of the patches from previous versions of the spec had been upstreamed — thanks Ossi — and only the bogus cruft patches remain like dragging in extra libraries and dealing with PTRACE.

The resulting qtcreator.bin works reasonably well — there’s an issue in detecting where Qt is installed, so I had to set that manually and the RPATH isn’t set to include lib/qtcreator/ — which means the method-autocompletion works and it does compile and run an application. I haven’t tried debugging or anything complicated, though.

This bit of Qt coding was in between my talk — on license selection and governance models in Free Software projects, where I was glad to have received useful feedback from the GNU hackers meeting yesterday — and a talk by Christina Haralanova. Just enough time to compile once, and it works.

Tags: , ,

2 Responses to “QtCreator on OpenSolaris”

  1. Mike Harrison Says:


    I am currently trying to get QtCreator compiled on Solaris 10, 64-bit, and am having problems because ptrace isn’t supported on this platform with 64-bit. The man page states it has been replaced by /proc. I can get creator to compile by commenting out the ptrace include and calls, but then I have no gdb functionality.

    Your post here was enticing because it mentions “dealing with PTRACE” with QtCreator. Have you encountered the same issue, and does a patch/fix exist that you could point me to? Thanks!


  2. adridg Says:

    All the sources and patches can be found at the KDE4-Solaris Mercurial repo (; I think I ended up #defining the relevant values and hoping it would work — I have not actually *tried* the gdb functionality.