You can run the “patch” command to apply the patch provided here. For example, suppose your Qt resides in /usr/local/qt-mac-opensource-src-4.3.3. You would need to change directory to /usr/local and run the following command:

patch -p0 < /path/to/patch.txt

If you are not comfortable with doing this, you can manually edit the code. Just look at the patch.txt file and you will notice that only a few lines changed. I added the following lines around the generation of the project:

bool is_sdk = (library.endsWith(”.sdk”));
if (!is_sdk)
{
…
…
…
}

The area should be easy to find my looking at the top of patch.txt. You can locate this area by finding the following line in that file:

bool is_frmwrk = (library.endsWith(”.framework”));

Also, the source for qmake is easy to find just by looking at the top of the patch file as well. Line 2 shows which file is being patched, in this case it is:

qt-mac-opensource-src-4.3.3/qmake/generators/mac/pbuilder_pbx.cpp

so qmake source code in located in /usr/local/qt-mac-opensource-src-4.3.3/qmake

after applying the patch you can change over to this directory and run make.

I hope this helps out. Please let me know if you have any additional questions.

Erm…how? Not all of us are Unix gods

How do you actually apply this ‘patch’ and rebuild just qmake? I couldn’t even find the source for it.

I couldn’t resist myself dreaming of having this Tokens.xml file as well, so I could do the API search and use my beloved option+click on classes and methods.

So I quickly whipped together a python script, which parses the functions.html and classes.html for class names and functions belonging to it. The script then takes all this class and function data and transforms it into a giant (13467 tokens) Tokens.xml file.

The Tokens.xml goes in the same directory as the Nodes.xml and after running the docsetutil, Xcode can now also show the Qt docs from within my code.

I’ve put up the python script and a convenient Tokens.xml file (for Qt 4.4.1) up at google code: xcode-tokens-from-qtdocs. Follow the link.

I hope it’s useful for others as well.

What would be even better of course, if there was some way to create the Tokens.xml file out of Trolltech’s Documentation.
With such a file we would be able to also use the fast API search, and the *incredible* helpful option click on a token in the code editor (e.g. class name or method).