On Saturday 23 February 2008 05:29:29 am Alexander E. Patrakov wrote: > > While I see no reason why this shouldn't work for LFS (because LFS > sets $QTDIR unconditionally), I must say that this is not how big > distros like Debian work. In Debian, Qt is in /usr, and there is no > $QTDIR in the environment (and QT/KDE applications build and work > just fine because pkgconfig supplies the needed flags correctly). > See, e.g., how the linux-2.6.24/scripts/kconfig/Makefile attempts to > find out how to use Qt (look below the "# QT needs some extra > effort..." line). > > -- > Alexander E. Patrakov
Yes, the extra flags are not necessary to provide if Qt and kdelibs are installed in /usr. The commands could be left as is, with a note saying extra stuff is necessary if the libraries are located elsewhere. My thoughts were to just provide one set of commands that will work, assuming you are building from an lfs system, then explain them, rather than different commands for different situations. Could also replaceable text, e.g. LD_LIBRARY_PATH='<Qt Prefix>' make, instead of a variable, but I personally don't like this method. It's not c'n'p friendly, and I'm sure that's what most users do instead of actually typing out all the commands. If a more correct and elegant solution comes up, I'm all for it. I'll take a look at that Makefile, see if I find anything useful that I understand. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
