[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease |
Date: |
Thu, 1 Sep 2016 00:57:20 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0 |
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/
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, (continued)
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Dan Sebald, 2016/08/30
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Mike Miller, 2016/08/30
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Dan Sebald, 2016/08/30
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Tatsuro MATSUOKA, 2016/08/30
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Tatsuro MATSUOKA, 2016/08/30
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Dan Sebald, 2016/08/30
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Dan Sebald, 2016/08/31
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Tatsuro MATSUOKA, 2016/08/31
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Dan Sebald, 2016/08/31
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Tatsuro MATSUOKA, 2016/08/31
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease,
Mike Miller <=
- [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease, Dan Sebald, 2016/08/31
- Prev by Date:
[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease
- Next by Date:
[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease
- Previous by thread:
[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease
- Next by thread:
[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease
- Index(es):