[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease

[Mike Miller]

Follow-up Comment #15, bug #48881 (project octave):

I think that's way too complicated for what this is intended to do.

qtchooser is simply a drop-in proxy executable that is symlinked and used in
place of moc, uic, etc.

The bug here is that if Octave sees qtchooser in PATH, then it assumes that
moc, uic, etc are all symlinks to qtchooser. This falls apart in the corner
case where you have a distro-installed version of Qt that uses qtchooser
(where they are symlinks and everything normally works as expected), but you
want to use a self-compiled version of Qt that is not configured for
qtchooser, and you have set PATH to include /usr/local/lib/qt-whatever/bin
containing the real executables.

I think configure should automatically discover whether moc, uic, etc, are
actually using qtchooser or not, *not* require the user to add an option to
force that kind of thing. And we should *not* need to set MOC to be something
odd like "qtchooser --run-tool=moc", and we should *not* need to support
additional arbitrary named configurations like "myqt5".

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48881>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/