P2: Important Description
Qt 4.8.1 binary packages for Mac are being released as part of the Qt 4.8 release program, run by Digia.
These binary packages install Qt into /System/Library/Frameworks and as a result:
sarasmit@bq-imacdev1:~/build/qt$ which qmake /usr/bin/qmake sarasmit@bq-imacdev1:~/build/qt$ ls -la /usr/bin/qmake lrwxr-xr-x 1 504 wheel 9 28 Mar 15:40 /usr/bin/qmake -> qmake-4.8 sarasmit@bq-imacdev1:~/build/qt$ qmake -query QT_INSTALL_PREFIX:/ QT_INSTALL_DATA:/usr/local/Qt4.8 QT_INSTALL_DOCS:/Developer/Documentation/Qt QT_INSTALL_HEADERS:/usr/include QT_INSTALL_LIBS:/Library/Frameworks QT_INSTALL_BINS:/Developer/Tools/Qt QT_INSTALL_PLUGINS:/Developer/Applications/Qt/plugins QT_INSTALL_IMPORTS:/Developer/Applications/Qt/imports QT_INSTALL_TRANSLATIONS:/Developer/Applications/Qt/translations QT_INSTALL_CONFIGURATION:/Library/Preferences/Qt QT_INSTALL_EXAMPLES:/Developer/Examples/Qt/ QT_INSTALL_DEMOS:/Developer/Examples/Qt/Demos QMAKE_MKSPECS:/usr/local/Qt4.8/mkspecs QMAKE_VERSION:2.01a QT_VERSION:4.8.1
Since Qt3D in developer mode will try to put its libraries into $$QT_INSTALL_LIBS during compile, this will fail (unless the build is done as root, which is very unwise).
The best option is to build Qt 3D 1.0 against the 4.8 support inside the Qt SDK. Since the SDK installs into the home directory and write permissions are OK there, it works well. If someone really does want to build for 4.8, they will need to do a package build and then run a make install step as root.
So it looks like we need to update the build instructions for this case.