QtForum.org

I'm having difficulty getting the Open Source version of 4.3.3 to build/install correctly on my Linux (F7) box. Specifically, I'm encountering what I believe to be path problems stemming from an incorrect or incomplete build. I have identified the following three problems so far:

1) Qt Assistant unaware of where built/installed documentation sources are. Looking in
'/usr/share/doc/qt4/html' (can fix with a symlink)

2) qtdemo -- various screens display summary message complaining of inability to find demo documentation. Above symlink hack does NOT change behavior.

3) qtdemo -- unable to launch any demo (executables are built and run individually from the 'demos' directory).

I have tried configuring with A) '-prefix-install' for a local sand-boxed build, B) no '-prefix' option at all, and C) my preferred install path of '-prefix /opt/Qt-4.3.3' and all builds/installs exhibit the same behaviors. 'make uninstall', 'make confclean', and rm -fr on the source tree have been used in various combinations to ensure each build is properly configured. The current 'configure' cocktail is as follows:

./configure -prefix /opt/Qt-4.3.3 -debug -shared -no-fast -largefile -exceptions \
-accessibility -stl -qt-sql-ibase -qt-sql-mysql -qt-sql-sqlite -qt-sql-sqlite2 -qt-sql-odbc \
-qt-sql-psql -qt3support -system-zlib -qt-gif -system-libtiff -system-libpng \
-system-libmng -openssl -no-rpath -continue -verbose -optimized-qmake -nis \
-cups -iconv -pch -qdbus -no-nas-sound -opengl -sm -xshape -xinerama -xcursor \
-xfixes -xrandr -xrender -fontconfig -tablet -xkb -separate-debug-info -glib

I don't mid the symlink hack to fix Qt Assistant but do feel something is incomplete with the configure/install or I wouldn't have to bother with it in the first place. I do mind qtdemo not working right -- I'm trying to migrate from Qt3 and broaden my skills as I go and it's a handy reference (my Windows 4.3.3 install works perfectly but I prefer to develop under Linux).

I have completed the full configure/make/sudo'ed make install cycle now several times and burned many hours on this. Can anyone advise as to what's up with the broken qtdemo and path(s)? I'm pretty good with Autotools but am missing something here.

Thanks in advance,
Bill

After digging through the qtdemo sources it appeared that QLibraryInfo might not be returning correct information for the various paths (documentation, demos, & examples). It was still unclear to me why this was -- everything appeared to install to the locations I wanted. I even tried explicitly setting all path components using '-prefix' and friends just in case the build process was improperly defaulting some of the component values but no luck.

I 'fixed' the problem by blowing the whole source tree away and installing via 'yum'.

This will get me by for initial development but I'd really like to know why the tarball install was failing for me in case I need to tweak certain build options. If anyone has any feedback please post.