Another thing that comes to my mind, that will break when renaming tools,
instead of installing links in paths like "/usr/bin" and keeping the the tools
unrenamed in specific version directories:
At the moment one can define an "external tool" in Qt Creator.
Configuration of these external tools is in Environment > External Tools, you
can define any executable to run there with arguments etc, and a menu item for
the tool will be shown in Tools > External.
E.g. we ship by default with an external tool definition for running lupdate
and lrelease, and the "executable" we run is defined as:
%{CurrentProject:QT_INSTALL_BINS}/lrelease
Qt Creator resolves that variable in there by taking the current project,
taking the current Qt version setting for that project, and asking that Qt
version for "qmake -query QT_INSTALL_BINS".
At the moment that should work for Qt4 and Qt5.
If you rename lrelease to lrelease5 (or any other tool that we ship), this is
no longer possible and gets pretty fancy.
++ Eike
On 19 Oct 2012, at 01:10, Thiago Macieira <[email protected]> wrote:
> On sexta-feira, 19 de outubro de 2012 01.03.29, André Pönitz wrote:
>> On Thu, Oct 18, 2012 at 08:30:03AM -0700, Thiago Macieira wrote:
>>> lconvert -> lconvert5
>>> lrelease -> lrelease5
>>> lupdate -> lupdate5
>>
>> Sorry, I don't get the joke.
>
> Because it was no joke. It's serious.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel Open Source Technology Center
> _______________________________________________
> Development mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/development
--
Eike Ziller, Senior Software Engineer - Digia, Qt
Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB
144331 B
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
