> >> The freeciv-qt binary is not built on my system. > > > > One difference would be, that the clean cowbuilder chroot will not > > have any qt development files installed, as they are not > > essential for building anything at all, nor a build-dependency of > > freeciv, so there will be no way the freeciv-qt binary *can* be > > built, even if there were a strong urge to build it if > > possible... > > That's an important piece of information here. So you are not > building in a clean chroot environment.
Indeed. I am not. > > Apparently, the configure step does not fail if the qt client is > > requested, and the qt headers etc. were not found... > > It is true that we pass --enable-client=all to the build system but > since we are not build-depending on any qt-libs which are necessary > to build freeciv-qt the build will not fail on the buildd server. I > see that this can lead to some confusion when people are not > building in a clean environment. I will instead pass > > --enable-client=gtk2,gtk3,sdl,xaw,stub > > to the configure step explicitly. I hope that helps. I assume it will. Thanks very much. Rogier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
