Re: GUI no longer building by default

[Torsten]

On 16.03.2013 09:17, Daniel J Sebald wrote:
> On 03/16/2013 03:02 AM, Torsten wrote:
>> On 16.03.2013 06:38, Daniel J Sebald wrote:
>>> On 03/16/2013 12:30 AM, Daniel J Sebald wrote:
>>>
>>>> similar to the following existing loop inside the configure script
>>>>
>>>> for ac_prog in moc-qt5 moc-qt4 moc
>>>
>>> BTW, should the "moc" come first?  I.e.,
>>>
>>>   for ac_prog in moc moc-qt5 moc-qt4
>>>
>>> What that would allow is for the system to define a symbolic link "moc"
>>> to either "moc-qt5" or "moc-qt4".  Or is that a bad thing to do?
>>
>> Nice idea, but the order used so far makes sure the newest qt-version is
>> found. If we want to allow symbolic links to tools of the desired
>> qt-version I would suggest to introduce a name that is not used by qt
>> itself, i.e.
>>
>>    for ac_prog in octave-moc moc-qt5 moc-qt4 moc
>>
>> Then, octave-moc is the name of the link to the qt-version to use.
> 
> I suppose the advantage is for the developer who wants to switch between
> Qt 4 and Qt 5 without having to go through the "configure" step again.
> Does it make sense to switch back and forth that way?  Is Qt 5 backward
> compatible?  Maybe we should just wait until we cross that bridge, i.e.,
> someone finds a need for that.  I was thinking more along the lines if
> the system were to link "moc" to be either "moc-qt5" or "moc-qt4".  I'm
> not sure it does that though.  Sounds like you've found "moc" to be
> something different.

No, I just had in mind the case where there is no link and there is
found a file named "moc". I am not sure if this file then really is
related to the newest qt-version ... okay, wait ... a better solution
from John just popped up in the mailing list.

Torsten