[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GUI no longer building by default
From: |
Torsten |
Subject: |
Re: GUI no longer building by default |
Date: |
Sat, 16 Mar 2013 09:02:08 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 |
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.
Torsten
- GUI no longer building by default, Daniel J Sebald, 2013/03/16
- Re: GUI no longer building by default, Daniel J Sebald, 2013/03/16
- Re: GUI no longer building by default,
Torsten <=
- Re: GUI no longer building by default, John W. Eaton, 2013/03/16
- Re: GUI no longer building by default, Daniel J Sebald, 2013/03/16
- Re: GUI no longer building by default, Mike Miller, 2013/03/16
- Re: GUI no longer building by default, Daniel J Sebald, 2013/03/16
- Re: GUI no longer building by default, Mike Miller, 2013/03/16
- Re: GUI no longer building by default, Daniel J Sebald, 2013/03/16
Re: GUI no longer building by default, marco atzeri, 2013/03/16